Bug 10507 – when using an editiable WebKit foreign namespace element are moved out of the document's head

• Status: RESOLVED
• Resolution: INVALID
• Component: DOM

[Robert Burns]

when using an editiable WebKit foreign namespace element are moved out of the document's head. This can be verified with Blot.app. Opening a document with elements such as ev:listener or listener or xforms:model or xforms get moved out of the heead upon opening.

[Robert Burns]

Created attachment 10160 [details]
sample xhtml file for reproducing bug in Blot.app

[Robert Burns]

the description should read: "... xforms:model or mdoel in the head"

[Mark Rowe (bdash)]

While this may not be relevant, the document you have attached doesn't validate as XML.  When loading it in Safari I get:
    This page contains the following errors:
    error on line 7 at column 20: Attribute lang redefined

A nightly build of WebKit produces:
    This page contains the following errors:
    warning on line 5 at column 33: xmlns:ev: 'www.w3.orgâ??xml-events' is not a valid URI
    error on line 8 at column 1: Attribute lang redefined

On closer inspection it seems as though your namespace declaration for "ev" has an EM DASH in place of the first hyphen.  I'm not sure if this, and the warning it produces, are relevant to the issue at hand but it could be worth fixing it and testing.

[Robert Burns]

(In reply to comment #3)
> While this may not be relevant, the document you have attached doesn't validate
> as XML.  When loading it in Safari I get:
>     This page contains the following errors:
>     error on line 7 at column 20: Attribute lang redefined
> 
> A nightly build of WebKit produces:
>     This page contains the following errors:
>     warning on line 5 at column 33: xmlns:ev: 'www.w3.orgâ??xml-events' is not
> a valid URI
>     error on line 8 at column 1: Attribute lang redefined
> 
> On closer inspection it seems as though your namespace declaration for "ev" has
> an EM DASH in place of the first hyphen.  I'm not sure if this, and the warning
> it produces, are relevant to the issue at hand but it could be worth fixing it
> and testing.
> 

[David Kilzer (:ddkilzer)]

(In reply to comment #4)

See Bug 6314 Comment #28.

[Lucas Forschler]

Mass moving XML DOM bugs to the "DOM" Component.