Hi there, while writing the Change Proposals, I noticed that 1) The current algorithm still breaks RFC 2616 in a way I thought was already fixed (see <http://www.w3.org/Bugs/Public/show_bug.cgi?id=9628#c3>); I have reopened that bug. And 2) The current algorithm accepts even more invalid sequences, and it's totally not clear whether those violations are needed; no matter what, they are currently not spelled out in the "willfull violation" note. The *simplest* fix would be to replace the whole subsection with an explanation how to parse the attribute value *properly*. We may want to look into this in case we come to the conclusion that we really don't have to be non-compliant to the spec defining the syntax. Best regards, JulianReceived on Saturday, 13 November 2010 18:06:00 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:27 UTC