Bug 126306 - Results of getBoundingClientRect() is wrong for fragmented element
Summary: Results of getBoundingClientRect() is wrong for fragmented element
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: http://lists.w3.org/Archives/Public/w...
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-12-30 14:49 PST by Dirk Schulze
Modified: 2022-08-20 18:17 PDT (History)
10 users (show)

See Also:

Attachments
Safari 15.6.1 and STP 151 differ and all other browsers with each other (1.47 MB, image/png)
2022-08-20 06:34 PDT, Ahmad Saleem 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Schulze 2013-12-30 14:49:15 PST 
getBoundingClientRect() maybe should return the closest rectangle including the border-box of the element as well as the border-box of all ancestors. Right now, it returns the dimension of the element based on the first fragment.

http://jsfiddle.net/6LkvZ/
Comment 1 Ahmad Saleem 2022-08-20 06:34:34 PDT 
Created attachment 461759 [details]
Safari 15.6.1 and STP 151 differ and all other browsers with each other

Just wanted to share updated results and screenshot:

*** Safari 15.6.1 / Safari Technology Preview ***

width: 333.5625 height: 140

*** Firefox Nightly 105 ***

width: 333.6000061035156 height: 139.11666870117188

*** Chrome Canary 106 ***

width: 333.5859375 height: 147

________

Please refer to above results. Thanks!
Comment 2 Radar WebKit Bug Importer 2022-08-20 18:17:10 PDT 
<rdar://problem/98934884>