NEW 50609
Selection ending in a non-editable span inside a editable div is rendered incorrectly
https://bugs.webkit.org/show_bug.cgi?id=50609
Summary Selection ending in a non-editable span inside a editable div is rendered inc...
Mark Tsui
Reported 2010-12-06 18:35:13 PST
What steps will reproduce the problem? 1. Open up the attached file. 2. Place cursor in the text "start selection here" 3. Press shift+right to expand selection to the right until it reaches "glitch" 4. Notice that as the selection expands, before selecting the "g" the entire contenteditable region becomes visibly selected. What is the expected result? The selection should expand and include the previous selection + "g" character What happens instead? The entire contenteditable appears selected. Please provide any additional information below. Attach a screenshot if possible. In other browsers, it takes two shift+right to move across the nested spans. Additional notes- the selection is rendered over the entire region, but if the selection is programmatically queries in JS returns the correct result.
Attachments
Test case (284 bytes, text/html)
2010-12-06 19:29 PST, Mark Tsui
no flags
reduction (504 bytes, text/html)
2011-09-19 13:39 PDT, Ryosuke Niwa
no flags
Mark Tsui
Comment 1 2010-12-06 19:29:35 PST
Created attachment 75773 [details] Test case
Ryosuke Niwa
Comment 2 2011-09-19 13:39:17 PDT
Created attachment 107912 [details] reduction
Ryosuke Niwa
Comment 3 2011-09-19 13:40:20 PDT
Confirmed on ToT WebKit.
Ahmad Saleem
Comment 4 2022-08-30 05:00:44 PDT
All browser differ: If I place my cursor after "here"(|) [before space] and do Shift+Right Arrow: > STP 152 takes two Shift+Right before selecting "G" from glitch > Chrome Canary 107 takes five Shift+Right before selecting "G" from glitch > Firefox Nightly 106 takes four Shift+Right before selecting "G" from glitch ______ I am not sure on web-spec and which behavior is ideal but just want to share updated testing results. Thanks!
Radar WebKit Bug Importer
Comment 5 2022-08-30 09:49:35 PDT
Note You need to log in before you can comment on or make changes to this bug.