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

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

From: <bugzilla@wiggum.w3.org>
Date: Wed, 25 Nov 2009 11:53:10 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-8372-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8372

           Summary: Restore <spacer> parsing as void element
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Some time during the past 9 months or so, the spec has regressed <spacer>
parsing by making it no longer parse as a void element.

Since the parsing section is mandatory and the rendering section is optional,
it seems that the easiest way to address the non-support of <spacer> in most
browsers while avoiding poking at sunk cost too much would be making the
element parse as a void element.

This also seems like the safer bet, considering that there are instances of the
<spacer> element out there (particularly on pages created with Adobe GoLive 4).


-- 
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 11:53:19 UTC

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