197042 2019-04-17 16:54:50 -0700 Range.getBoundingClientRect returns invalid bounds when between two non-editable nodes 2026-01-28 17:41:53 -0800 1 1 1 Unclassified WebKit DOM Safari Technology Preview Mac macOS 10.14 NEW https://bugs.webkit.org/show_bug.cgi?id=196380 InRadar P2 Normal --- 1 shrey webkit-unassigned ahmad.saleem792 ap bfulgham karlcow megan_gardner rniwa simon.fraser webkit-bug-importer wenson_hsieh zalan oldest_to_newest 1528340 0 367698 shrey 2019-04-17 16:54:50 -0700 Created attachment 367698 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 1528465 1 webkit-bug-importer 2019-04-18 09:23:50 -0700 <rdar://problem/50017853> 1890093 2 ahmad.saleem792 2022-08-09 13:58:13 -0700 I am able to reproduce this bug in Safari 15.6 on macOS 12.5 and get following using attached test case and looking into Console: >>> DOMRect bottom: 0 height: 0 left: 0 right: 0 top: 0 width: 0 x: 0 y: 0 In other browsers, I get following: *** Chrome Canary 106 *** Same as Safari 15.6 *** Firefox Nightly 105 *** bottom: 8 height: 0 left: 8 right: 8 top: 8 width: 0 x: 8 y: 8 _______ I am not sure on web-spec but just wanted to update latest test results. Thanks! 2176028 3 karlcow 2026-01-28 17:41:53 -0800 This is a duplicate of Bug 54813 I believe 367698 2019-04-17 16:54:50 -0700 2019-04-17 16:54:50 -0700 You can open it in Safari and look at the console log to see the bug getBoundingClientRect-bug.html text/html 454 shrey PGh0bWw+Cjxib2R5PgogICAgPGRpdiBjb250ZW50ZWRpdGFibGU9InRydWUiPgogICAgICAgIDxz cGFuIGNvbnRlbnRlZGl0YWJsZT0iZmFsc2UiPkE8L3NwYW4+CiAgICAgICAgPHNwYW4gY29udGVu dGVkaXRhYmxlPSJmYWxzZSI+Qjwvc3Bhbj4KICAgIDwvZGl2Pgo8L2JvZHk+CjxzY3JpcHQgdHlw ZT0idGV4dC9qYXZhc2NyaXB0Ij4KICAgIGNvbnN0IGNvbnRhaW5lciA9IGRvY3VtZW50LmJvZHku Zmlyc3RDaGlsZDsKCiAgICAvLyBDcmVhdGUgYSByYW5nZSBiZXR3ZWVuIEEgYW5kIEIKICAgIGNv bnN0IHJhbmdlID0gZG9jdW1lbnQuY3JlYXRlUmFuZ2UoKTsKICAgIHJhbmdlLnNldFN0YXJ0KGNv bnRhaW5lciwgMSk7CiAgICByYW5nZS5zZXRFbmQoY29udGFpbmVyLCAxKTsKCiAgICBjb25zb2xl LmxvZyhyYW5nZS5nZXRCb3VuZGluZ0NsaWVudFJlY3QoKSk7Cjwvc2NyaXB0Pgo8L2h0bWw+Cg==