- From: David Carlisle <davidc@nag.co.uk>
- Date: Thu, 08 Mar 2012 10:19:49 +0000
- To: public-xml-er@w3.org
On 08/03/2012 02:42, David Lee wrote: > Q: when you talk about "browser use case" are you talking about > requiring the browsers code to change ? the most useful way for any of this to work in browsers would require code change. You could implement an xml-er parser in JS but that doesn't really address the main issue which is browsers navigating to application/xml or application/xhtml+xml pages which are not well formed and wanting to do something more friendly than a "yellow screen of death". Thus it has to hook into (in place of) the current xml parse. If xml-er is only usable in the browser via a javacript api called from an html page then it's a lot less useful. > or is this something that can > be implemented in JavaScript or as an addoon. Why I ask is that if > the browsers need to change I'm pretty certain this is a dead end > without browser vendors being involved in this discussion. Well they are watching, I'm sure and Anne works for Opera, but you can't expect them to say at this stage whether they would do anything. > But if its > something that can plugin to existing browsers then we don't need > them :) > David ________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________
Received on Thursday, 8 March 2012 10:20:18 UTC