W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2009

[Bug 8372] Restore <spacer> parsing as void element

From: <bugzilla@wiggum.w3.org>
Date: Wed, 25 Nov 2009 13:45:15 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NDIBH-0003Y9-3b@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8372





--- Comment #4 from Henri Sivonen <hsivonen@iki.fi>  2009-11-25 13:45:14 ---
(In reply to comment #3)
> Which DOM interface do you think spacer should have?

Apparently HTMLSpacerElement that is a mere marker interface that doesn't
differ from HTMLElement.

> Does supporting <spacer> in the rendering gain Web compat?

I flipped through the pages from
http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/tag/spacer in
both Firefox and Safari. I couldn't find a single page where the lack of
<spacer> support disadvantaged Safari in a noticeable way. I found one case
(the same that Maciej found) where you could spot a tiny disadvantage to Safari
when comparing pages side-by-side:
http://www.literaturkritik.de/public/rezension.php?rez_id=1547

I did notice that rendering the border around linked images disadvantaged
Firefox in some cases. https://bugzilla.mozilla.org/show_bug.cgi?id=452915

>From this data, it's hard to make the case that non-Gecko browsers should add
layout-level support for <spacer>.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 25 November 2009 13:45:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:05 UTC