Perhaps it's worth noting that in IE10, XML islands are treated in the
same way as Firefox/Chrome:
http://blogs.msdn.com/b/ie/archive/2011/07/06/html5-parsing-in-ie10.aspx
On 07/07/11 05:16, Fábio M. Costa wrote:
Just to clarify, it works with regular XML document (xml that you get
from ajax).
Yes, please create a ticket on slick's github.
If you wanna go further, fork slick on github, make the fix and send a
pull request.
Thank you for the report!
https://github.com/mootools/slick
https://github.com/mootools/slick/issues
--
Fábio Miranda Costa
frontend@portalpadroes
Globo.com
*github:* fabiomcosta
*twitter:* @fabiomiranda
*ramal:* 6476
On Wed, Jul 6, 2011 at 5:42 PM, Eric Patrick <[email protected]
<mailto:[email protected]>> wrote:
Fábio,
I believe Sandy is spot on.
I did indeed try Slick.search(document.getElementById('Config') ...;
IE 9 returns 0.
I also tried an HTML 5 data block using the script tag, but Slick does
not parse the XML as part of a script tag:
http://jsfiddle.net/HVSQZ/4/
So, I can use Slick to parse XML contained in:
- xml tag: broken in IE, since IE appears to return an XML node
instead of an HTMLUnknownElement
- random tag: cross browser, but would not pass HTML5 validation
- script tag (HTML 5 data block): broken in Chrome and IE (not tested
in FF)
http://www.w3.org/TR/html5/scripting-1.html
https://developer.mozilla.org/en/Using_XML_Data_Islands_in_Mozilla
---
Would you recommend that I submit a ticket to modify Slick to work
with the HTML 5 data block, or is my use case inappropriate for Slick?
Thanks for the feedback gentlemen,
Eric
On Jul 6, 2:47 pm, Sanford Whiteman <[email protected]
<mailto:[email protected]>>
wrote:
> Think the problem here is that in IE, this is a "real" XML
island with
> associated proprietary methods, while in the other
browsers it's
> essentially an HTMLUnknownElement.
>
> -- Sandy
--
Barry van Oudtshoorn
www.barryvan.com.au
Not sent from my Apple ?Phone.
