In the in body insertion mode, shouldn't the eod-of-file token
case have a special handling of if the current node is a plaintext
element and not generate a parse error in this case?
The current behavior is that if you use plaintext, you'll have a
parse error at EOF. Is this intended?
--
Thomas
On Wed, 12 Mar 2008 16:53:52 +0100, Thomas Broyer [EMAIL PROTECTED]
wrote:
In the in body insertion mode, shouldn't the eod-of-file token
case have a special handling of if the current node is a plaintext
element and not generate a parse error in this case?
The current behavior is that if you
Dnia 11-03-2008, Wt o godzinie 19:31 +, Tom Gilder pisze:
On Tue, Mar 11, 2008 at 6:15 PM, Krzysztof Żelechowski
[EMAIL PROTECTED] wrote:
I see no point in returning true when there are no links to remove. IE
and Opera currently only return true when the selection contains a
link.
On 5th June 2007, Øistein E. Andersen wrote:
(To do this properly, what we really ought to do is look for
C1 and undefined characters in all IANA charsets and semi-official
mappings to Unicode and check 1) whether the gaps can be filled
by borrowing from other encodings, and 2) whether
On Wed, 12 Mar 2008, Thomas Broyer wrote:
In the in body insertion mode, shouldn't the eod-of-file token case
have a special handling of if the current node is a plaintext element
and not generate a parse error in this case?
The current behavior is that if you use plaintext, you'll have a
