| Summary: | Display Error: empty object renders with a space in Safari, different in FF | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Cameo Wood <cameowood> | ||||
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | 01-reg, anantha, aroben, ian, jddcef, jon, mitz, mrowe, webkit | ||||
| Priority: | P2 | Keywords: | HasReduction, InRadar | ||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| URL: | http://youthoughtwewouldntnotice.com/blog3/?p=647 | ||||||
| Attachments: |
|
||||||
|
Description
Cameo Wood
2008-01-11 10:42:27 PST
It's almost like Firefox is doing <object> fallback for empty object elements (so they turn into spans effectively and then the width/height is ignored). It's not clear to me if that should be done or not, since technically there is nothing to fall back to. I'd say the following two tests should be handled the same: data:text/html,<p><object height="350" width="425"></object></p> data:text/html,<p><object height="350" width="425">X</object></p> I don't think we should change fallback behaviour just because the element is empty. This is related and possibly a dupe of 15205. Created attachment 18982 [details]
Minimal test case
*** Bug 15205 has been marked as a duplicate of this bug. *** *** Bug 10622 has been marked as a duplicate of this bug. *** Hyatt, Hixie: if you two disagree with FF's behavior, it would be great if you could file a bug with them. It seems real world websites depend on this (given the dupes we've seen reported). Oh, and BTW, this is not just FF which we're differing from. FF is just matching IE's behavior here. IE collapses empty <object> tags as well. *** Bug 21482 has been marked as a duplicate of this bug. *** |