getBoundingClientRect() wrong for XHTML embedded in SVG




6 years ago
6 years ago


(Reporter: Gavin Kistner, Unassigned)


7 Branch
Windows 7

Firefox Tracking Flags

(Not tracked)



(1 attachment)



6 years ago
Created attachment 572648 [details]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.21 Safari/535.7

Steps to reproduce:

Embedded XHTML inside a <foreignObject> inside SVG and asked for the getBoundingClientRect() of an HTML element therein.

Actual results:

Received coordinates of the element within the embedded `<body>` inside the SVG document, not affected by the scaling or placement of the `<foreignObject>` inside the SVG container.

Expected results:

Received coordinates relative to the viewport of the browser window.

Comment 1

6 years ago
View the test file hosted here:

The actual application was the desire to find the location in SVG coordinate space of embedded XHTML contents, in order to connect SVG elements to the embedded HTML contents, as seen here:

The proposed technique is to translate the embedded HTML element coordinates into screen space (using getBoundingClientRect()) and then transform those coordinates into a local SVG space. This works as intended on Chrome/Safari.
This is the behavior the spec calls for, as far as I can tell.  In particular, says:

  The getClientRects() and getBoundingClientRect() methods provide information about the
  position of the border box edges of an element relative to the viewport.

and says:

  Viewport and initial containing block are defined by CSS 2.1 unless there is an
  ancestor foreignObject element in the namespace in which
  case that element acts as viewport and initial containing block.
Or in other words, the return value for getBoundingClientRect in a <foreignObject> is in the coordinate system of that <foreignObject>; you can then use its CTM to do whatever else you want as described in comment 1.

Comment 4

6 years ago
Wow…right you are. I totally missed that definition of viewport. Looks like it's Webkit at fault here. :)
Last Resolved: 6 years ago
Resolution: --- → INVALID
Gavin, are you going to file a bug on WebKit, or should I?

Comment 6

6 years ago
Boris: I am planning on filing a bug. I think I could make a slightly clearer use case/repro case for them first.
Sounds good.  Thanks!

Comment 8

6 years ago
FWIW the corresponding Webkit bug is


6 years ago
Note also

Depending on the outcome of that, the spec (and our behavior) might change...

If you have thoughts on the issue, it'd be good to follow up on that mailing list.
You need to log in before you can comment on or make changes to this bug.