After much discussion recently with Erik, we decided that Safari was a lost cause when it came to coercing XML documents out of serialized strings. Fortunately, Safari 2.0.1 seems to now include both the DOMParser and XMLSerializer classes that Mozilla implements. Looks like some of the last chinks in Safari’s Ajax armor are finally fixed.
-
What’s All This Then?
I'm Alex Russell, a web developer working on Chrome, Blink, and the Web Platform at Google. I'm guilty of many JavaScript transgressions.
I help lead the team building a new application model for the web, and serve on ECMA TC39 (the standards body for JavaScript). I'm an elected member of the W3C Technical Architecture Group and am Tech Lead for Standards inside the Chrome team. I design and advocate for extensible, layered, data-driven evolution of the web platform.
My professional aim is to make the web a better platform and to the extent that I can keep politics and economics from creeping in, that's what this blog is about.
Other facets available upon HTTP request: twitter, facebook, flickr, linkedin, lanyrd, and quora. Expect less self-restraint there.
I'm proud husband to Frances Berriman. We live and work in San Francsico.
-
Recent Comments
- karl on Doing Science On The Web
- alex on Doing Science On The Web
- Dave Rupert on Doing Science On The Web
- Ravish on Doing Science On The Web
- Michael on Doing Science On The Web
- Aurelio De Rosa on A Funny Thing Happened On The Way To The Future…
- Ludovico Fischer on A Funny Thing Happened On The Way To The Future…
- alex on A Funny Thing Happened On The Way To The Future…
- Mike Johnson on A Funny Thing Happened On The Way To The Future…
- Justin Lawrence on Progressive Web Apps: Escaping Tabs Without Losing Our Soul
One Trackback
[…] They’ve implemented DOMParser for Safari (Safari added native support for this in it’s latest update). Just when we thought it was a lost cause. The DOMParser uses an HTML element and sets innerHTML on that. That was too simple for us to come up with […]