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

Re: [Bug 6670] Allow unescaped &s, at least in attributes that accept URLs

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 29 May 2009 11:24:01 +0200
Message-ID: <4A1FA9B1.3030000@gmx.de>
To: Ian Hickson <ian@hixie.ch>
CC: public-html@w3.org
Ian Hickson wrote:
> On Fri, 29 May 2009, Julian Reschke wrote:
>>> I've tried to do this. The spec text for this is highly unintuitive, 
>>> but I hope it matches practical intuition more than the previous text. 
>>> I'm not compeltely convinced that this is a good idea, so let me know 
>>> if you think this should be changed back.
>> If this mean that it's not conforming: -1!
> 
> I don't understand what you mean.

I meant: "If this mean that it becomes conforming (= "valid"): -1".

>> There are better ways to achieve shorter href attributes, such as using 
>> ";" instead of "&" as query parameter delimiter.
> 
> Unfortunately we are stuck with "&" for systems that use form submission.

How many of the escaped ampersands in the response to a Google Search 
are contained in href attributes that point to Google services? Fix 
those to accept ";" instead of "&", and replace them in the links.

Furthermore, there are other means to optimize for size, such as using 
gzip (which saves ~75% on the response I just tried), or using a 
client-side include mechanism for static parts of the page (this was 
proposed several times in the past, and rejected as not needed).

BR, Julian
Received on Friday, 29 May 2009 09:24:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:03 UTC