On Wed, 05 Aug 2009 02:01:59 +0200, Ian Hickson i...@hixie.ch wrote:
I'm pretty sure that character encoding support in browsers is more of a
collect them all kind of thing than really based on content that
requires it, to be honest.
Really? I think a lot of them are actually used. If you know
On Wed, 29 Jul 2009, Aryeh Gregor wrote:
On Wed, Jul 29, 2009 at 4:39 AM, Ian Hicksoni...@hixie.ch wrote:
Which others are needed for compatibility?
I don't know, but there are certainly some. Otherwise, why would
browsers support so many?
I'm pretty sure that character encoding
On Wed, 15 Jul 2009, Aryeh Gregor wrote:
In 2.4.4.1:
If position is not past the end of input, return to the top of the
step labeled loop in the overall algorithm (that's the step within
which these substeps find themselves).
Why not just go to step 9?
Which part specifically are you
On Wed, Jul 29, 2009 at 4:39 AM, Ian Hicksoni...@hixie.ch wrote:
There is value in not changing them unless they are actually broken --
when I edit the spec, there's always a risk I'll break something.
Okay, not a big deal then.
I've required UAs to catch this case and added this example.
In 2.4.4.1:
If position is not past the end of input, return to the top of the
step labeled loop in the overall algorithm (that's the step within
which these substeps find themselves).
Why not just go to step 9? In any event this is inconsistent with
2.4.4.2, which says
If position is not past
