W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10800] Reconsider form feed (U+000C) conformance

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 19:59:41 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P1PI5-00079C-5l@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10800

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |dbaron@dbaron.org,
                   |                            |eric@webkit.org,
                   |                            |ian@hixie.ch,
                   |                            |w3c@adambarth.com
         Resolution|                            |NEEDSINFO

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-30 19:59:40 UTC ---
The main reason this is allowed is that form feeds appear in documents such as
RFCs.

https://bugzilla.mozilla.org/show_bug.cgi?id=437915 suggests Mozilla already
does what the HTML spec says, though. I'm loathe to keep dragging implementors
back and forth on this. Furthermore, changing this would mean changing the
Gecko and WebKit HTML parsers, which treat U+000C like U+0020 in a whole bunch
of places.

We don't really gain anything by making U+000C illegal if we still let it
appear in the DOM (which we presumably would, as we do U+000B for example).

Furthermore, CSS syntactically agrees with the HTML spec here in terms of how
U+000C is handled (as whitespace). (I forget if that happened before HTML5 or
after, though.) It's not clear that it would be especially useful for U+000C to
collapse like U+0020 in 'white-space' handling, so I'm not really worried about
that.

So in conclusion, I don't know that it's worth changing anything here.


EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale:

Before changing anything here, we'd need at least Gecko and WebKit on board. I
know Henri would probably be happy to (finally, after years of trying to get me
to do this... sorry...) change Gecko accordingly, but can we get WebKit to
change the handling of U+000C everywhere? How about the CSS specs, would we be
able to get U+000C removed as syntactic whitespace there?

-- 
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 Thursday, 30 September 2010 19:59:42 UTC

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