Issue metadata
Sign in to add a comment
|
A html comment at the end of the text will affect copy&paste result
Reported by
yehchih...@gmail.com,
Oct 18 2017
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13) AppleWebKit/604.1.38 (KHTML, like Gecko) Version/11.0 Safari/604.1.38
Example URL:
Steps to reproduce the problem:
1. make a webpage like this:
<div>
<p>
line 1
<!-- useless comment !-->
</p>
<p>line 2</p>
<p>line 3</p>
</div>
2. open Chrome. Copy the content from the page
3. paste it into a plain-text editor
What is the expected behavior?
All three lines should have an empty line in between.
What went wrong?
Notice that between line 1 and line 2 there's no empty line. If there's no html comment like line 2, then it works just fine.
One would expect html comment does not change the result of copy & paste, but in fact it does.
Does it occur on multiple sites: Yes
Is it a problem with a plugin? No
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: Version 61.0.3163.100 (Official Build) (64-bit) Channel: stable
OS Version: OS X 10.13
Flash Version: Shockwave Flash 27.0 r0
,
Oct 20 2017
Unable to reproduce the issue on reported version 61.0.3163.100 and latest canary 64.0.3243.0 using Mac 10.12.6 @ yehchihwei: Could you please re-try the scenario by creating a new profile Please follow below steps to create a New profile (i). Launch chrome>>Press Alt+E>>Settings) (ii).Under the section headed People, Click on link Manage other people>>Add person If the issue still persists, please let us know your observation and provide the screenshot, that would help in triaging the issue from TE-end
,
Oct 20 2017
Hi Divya, I made a new profile, but the issue can still be reproduced, so do my friends. The plain text editor can be just a vim or something that's very simple. I am attaching a gif to show what's going on. Thanks, Chihwei
,
Oct 20 2017
Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 20 2017
,
Oct 23 2017
Able to reproduce the issue on reported version 61.0.3163.100, latest stable 62.0.3202.62 and latest canary 64.0.3247.0 using mac 10.12.6, Ubuntu 14.04 and win 10 Below is the Manual bisect info Good : 61.0.3145.0 - 483574 Bad: 61.0.3146.0 - 483866 working on tool bisect, will update the result soon
,
Oct 24 2017
Here is the Tool Bisect Info: --------------------------- You are probably looking for a change made after 483682 (known good), but no later than 483683 (first known bad) CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/203a2bad8062d170441af80f574e897bc586f180..7c44da721a59e6aa0b9fdcddb314175cb1e0123f Possible suspect: --------------- https://chromium-review.googlesource.com/517940 @Rune Lillesveen: Kindly take a look and please help us in reassign this issue to a right owner if not with respect to your change. Note: Unable to assign to Rune Lillesveen, hence assigning to Yoshifumi Inoue as one of the reviewers of the CL Thanks.!
,
Oct 24 2017
,
Nov 1 2017
The NextAction date has arrived: 2017-11-01
,
Dec 6 2017
futhark@, could you take look? It seems you change affect visible selection canaonicalization.
,
Dec 6 2017
,
Dec 6 2017
So: Fails: (a) <p>line 1 <!-- useless comment !--> </p> (b) <p>line 1<!-- useless comment !--></p> (c) <p>line 1 <!-- useless comment !--></p> Works: (d) <p>line 1<!-- useless comment !--> </p> (e) <p>line 1</p> The new fail here is (a). The reason is that my CL optimized away the LayoutText for the whitespace node because it's looking at the previous text node to see if it ends with a whitespace and concludes it doesn't need a whitespace renderer. It's just triggering the same issue as (b) and (c) afaict. The bug is that the code somehow incorrectly requires a LayoutText after the comment to be able to serialize correctly.
,
Dec 6 2017
,
Jan 10 2018
Lower to Pri-3 since we don't have enough resources to work this. This is caused by visible canonicalization and we need to have many changes to fix this issue.
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Oct 19 2017