<object> tags should treat width/height on a referenced SVG as intrinsic width/height
This bug came out of the comments from:
It might even be a duplicate of bug 10526, but it was hard for me to tell what exactly bug 10526 is about.
Hyatt and I (and I think jwatt or tor was present as well) talked about treating <svg> specified width/height as intrinsic height when using an SVG image in an <img> tag or CSS background image. In the comments of bug 10526 it was suggested that we also do so for <object> tags. Making this work would be a nice step in the direction of having real SVG in <img> support.
Created attachment 12026 [details]
test case to demonstrate the desired behavior
I should note, that I know of no browser which behaves the way this test case expects it to be have. Opera does not seem to use width for intrinsic size (at least 9.01 does not). Opera does seem to use the height attribute on the SVG for intrinsic height however.
Either way, this should be done after the SVGRenderRoot split, bug 12207.
(In reply to comment #1)
> Created an attachment (id=12026) 
> test case to demonstrate the desired behavior
> I should note, that I know of no browser which behaves the way this test case
> expects it to be have. Opera does not seem to use width for intrinsic size (at
> least 9.01 does not). Opera does seem to use the height attribute on the SVG
> for intrinsic height however.
I am not sure this testcase is correct. Needs discussion with Eric I think.
I think this is basically the same bug as:
One could probably be duped against the other.
We discussed the test case. It's correct.
is a good example of how we could do this. It is called when <canvas> changes size. We just need to add a similar method to RenderPartObject and have SVGSVGElement call it appropriately.
The real way to fix this is bug 15849.
This bug is still not solved. I have hit the problem myself. Here is an example:
Firefox 3 and opera 10 render it properly (not opera 9). I don't about IE with the appropriate plugin.
This has been tested on the last nighty build : r41707 on linux.
The patch on bug 10526 fixes this bug.
Fixed in r87526.
Re-opening because the fix that was originally landed is being reverted. See Bug 64974. Feel free to close this and open one of the many related ones if they do a better job describing the problem.
Closing again, the test case works fine and is covered by tests in trunk.