Bug 47729 - Provide a mechanism to get the tight bounding box of a container with 3D transformed elements
Summary: Provide a mechanism to get the tight bounding box of a container with 3D tran...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.6
: P2 Enhancement
Assignee: Nobody
URL: http://developer.apple.com/library/sa...
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2010-10-15 11:03 PDT by Antoine Quint
Modified: 2010-10-19 01:25 PDT (History)
1 user (show)

See Also:

Attachments
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 Antoine Quint 2010-10-15 11:03:51 PDT 
When dealing with 3D transformed content, the structural container may have zero-size CSS metrics. The Apple Finger Tips sample code is a good example (see URL). For instance, in that code the #ring element has 0x0 CSS metrics and getBoundingClientRect() reports width and height to be 0 and 0. It would be great to have a functionality to get the tight bounding box of such elements to hide away the complexity of dealing with 3D maths.
Comment 1 Antoine Quint 2010-10-15 11:04:43 PDT 
When dealing with 3D transformed content, the structural container may have zero-size CSS metrics. The Apple Finger Tips sample code is a good example (see URL). For instance, in that code the #ring element has 0x0 CSS metrics and getBoundingClientRect() reports width and height to be 0 and 0. It would be great to have a functionality to get the tight bounding box of such elements to hide away the complexity of dealing with 3D maths.
Comment 2 Antoine Quint 2010-10-15 11:05:13 PDT 
When dealing with 3D transformed content, the structural container may have zero-size CSS metrics. The Apple Finger Tips sample code is a good example (see URL). For instance, in that code the element with ID "ring" has 0x0 CSS metrics and getBoundingClientRect() reports width and height to be 0 and 0. It would be great to have a functionality to get the tight bounding box of such elements to hide away the complexity of dealing with 3D maths.
Comment 3 Antoine Quint 2010-10-19 01:25:43 PDT 
rdar://problem/8566867