Bug 91724 – Range object returns reversed rectangles in vertical text if parent element of text node is inline element

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: DOM

[Tatsuya Nitta]

Created attachment 153199 [details]
Test file to reproduce

Overview: 
  If parent element of text node is inline element and "vertical-rl" is set to -webkit-writing-mode, Range object returns reversed rectangles.

Steps to Reproduce:
  1) Open the attached test file which contains 4 <DIV> elements
     Each of them are: 
     (a) horizontal text in DIV element
     (b) vertical text in DIV element
     (c) horizontal text in SPAN element under DIV element
     (d) vertical text in SPAN element under DIV element
     Gray(#909090) colored DIV elements in 4 DIV element are generated by JavaScript which represents rectangles of Range object created from text node.
  2) See the gray(#909090) colored DIV elements in DIV element of (d)
  3) Open the inspector and select Elements button and then make sure rectangles are returned in reverse order 

Actual Results: 
  The rectangles are returned in reverse order, only when parent element of text node is inline element and "vertical-rl" is set to -webkit-writing-mode.
  
Expected Results:
  The rectancles should be returned in the correct order even if parent element of text node is inline element and "vertical-rl" is set to -webkit-writing-mode.

Additional Information:
  The rectangles are returned correctly when the text is horizontal or parant element of text node is block element.

[Tatsuya Nitta]

Created attachment 153202 [details]
Result screen shot

[Tatsuya Nitta]

Created attachment 153396 [details]
Test file to reproduce

[Tatsuya Nitta]

It's been a while since I logged this bug. It seems there is no update.
Can someone look at this issue?

[Ahmad Saleem]

I am not able to reproduce this selection bug in Safari 15.6 on macOS 12.5 from the shown in the reference screenshot. It is matching with the correct order selection from the reference as of today. Chrome Canary 106 also matches with Safari 15.6 but for some reason Firefox Nightly 105 has different behavior, which might be due to -webkit-writing-mode prefix. I didn't try to fix test case to check in Firefox considering that the reference screenshot incorrect behavior is not present anymore.

If you someone want, I can test it. Just wanted to share updated status and I think this can be marked as "RESOLVED CONFIGURATION CHANGED". If I am testing incorrectly, please test accordingly. Thanks!

[Brent Fulgham]

Sounds correct, thank you for testing!