On Mar 11, 2006, at 03:20, Ian Hickson wrote:
On Sun, 19 Feb 2006, Henri Sivonen wrote:
Off the top of my head, the changes from the HTML parsing output
involve
(besides lowercasing names and putting elements in the XHTML 1.x
namespace)
getting rid of the meta element conveying character
Ian Hickson wrote:
Yeah, I think the Mozilla behaviour on this was actually more correct, but
less useful (and less compatible) overall.
In fact usefullness of ins and del is pretty limited anyway. For
example you can't add a row to a table or an item to a list since
neither table nor ul
Hi,
From: Henri Sivonen [EMAIL PROTECTED]
BTW, the spec also says: If both the xml:lang attribute and the lang
attribute are set, user agents must use the xml:lang attribute, and the
lang attribute must be ignored for the purposes of determining the
element's language.
Shouldn't lang
On Mar 10, 2006, at 22:49, Ian Hickson wrote:
I'm actually considering just requiring that UAs support rewinding (by
defining the exact semantics of how to parse for the meta
header). Is
this something people would object to?
I think allowing in-place decoder change (when feasible) would
Quoting Ivan Sagalaev [EMAIL PROTECTED]:
Yeah, I think the Mozilla behaviour on this was actually more
correct, but less useful (and less compatible) overall.
In fact usefullness of ins and del is pretty limited anyway. For
example you can't add a row to a table or an item to a list since
On Mar 11, 2006, at 17:10, Henri Sivonen wrote:
Initialize a character decoder that the bytes 0x20–0x7E (inclusive)
as well as 0x09, 0x0A and 0x0D decode to the Unicode code points of
the same (zero-extended) value and maps all other bytes to U+FFFD
and raises a REWIND flag
On further
