[Webkit-unassigned] [Bug 197042] New: Range.getBoundingClientRect returns invalid bounds when between two non-editable nodes

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=197042

            Bug ID: 197042
           Summary: Range.getBoundingClientRect returns invalid bounds
                    when between two non-editable nodes
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Macintosh
                OS: macOS 10.14
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: DOM
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: shrey at quip.com

Created attachment 367698

  --> https://bugs.webkit.org/attachment.cgi?id=367698&action=review

You can open it in Safari and look at the console log to see the bug

I have attached a test case where you can see this in the console log, but also copying the description from the Chrome bug (#953977) I filed for this:

Steps to reproduce the problem:
1. Create a contenteditable=true node
2. Add two nodes inside it with contenteditable=false
3. Position a Range between these two programmatically or by clicking between them
4. Call getBoundingClientRect() on the current range

What is the expected behavior?
This should return the same bounds as it would if the two adjacent nodes were editable.

What went wrong?
This currently returns a DOMRect with everything zero-ed out:

bottom: 0
height: 0
left: 0
right: 0
top: 0
width: 0
x: 0
y: 0

Did this work before? No

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190417/253a52f8/attachment.html>