W3C home > Mailing lists > Public > public-html@w3.org > January 2011

Re: CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 18 Jan 2011 19:46:18 +0000 (UTC)
To: Sam Ruby <rubys@intertwingly.net>
cc: HTML WG <public-html@w3.org>
Message-ID: <Pine.LNX.4.64.1101181942300.28618@ps20323.dreamhostps.com>
On Tue, 18 Jan 2011, Sam Ruby wrote:
> On 12/01/2010 07:35 AM, Sam Ruby wrote:
> > The current status for this issue:
> > 
> > http://www.w3.org/html/wg/tracker/issues/126
> > http://dev.w3.org/html5/status/issue-status.html#ISSUE-126
> > 
> > We have a single change proposal to parse backslashes in Content-Type
> > headers in <meta> elements in a HTTP compliant manner:
> > 
> > http://lists.w3.org/Archives/Public/public-html/2010Nov/0234.html
> > 
> > At this time the Chairs would also like to solicit alternate Change
> > Proposals (possibly with "zero edits" as the Proposal Details), in case
> > anyone would like to advocate the status quo or a different change than
> > the specific one in the existing Change Proposals.
> > 
> > If no counter-proposals or alternate proposals are received by January
> > 12th, 2011, we will proceed to evaluate the change proposal that we have
> > received to date.
> 
> As we have received no counter-proposals or alternate proposals, the 
> chairs are issuing a call for consensus on the proposal that we do have.  
> If no objections are raised to this call by 26 January 2011, we will 
> direct the editor to make the proposed change.  If anybody would like to 
> raise an objection during this time, we strongly encourage them to 
> accompany their objection with a concrete and complete change proposal.

This is not an objection, but for the record, it is most definitely the 
case that no browsers implement what Julian is suggesting here, so making 
this change to the spec would lead us further away from interoperability 
on the short term, and would be an implementation cost for all user agents 
with no apparent long-term benefit.

If browser vendors are concerned with this, they should either write a CCP 
to object to it, or fail to implement Julian's proposal. My goal is to 
update this section of the spec in a few years to match whatever browsers 
converge on.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 18 January 2011 19:46:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:18 GMT