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

Julian, your change proposal claims that this is not needed for
interoperability. Do you have any data showing this other than the
fact that webkit-based browsers and opera does not implement this?
Have you searched the open bug databases for webkit to see if there
have been any bugs filed on this?

My experience is that just because webkit and opera doesn't implement
a particular quirk doesn't mean it's not needed for web compatibility.

/ Jonas

On Tue, Jan 18, 2011 at 8:25 AM, Sam Ruby <rubys@intertwingly.net> 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.
>
>> - Sam Ruby
>
> - Sam Ruby
>
>
>

Received on Wednesday, 19 January 2011 04:07:26 UTC