- From: Travis Leithead <travil@windows.microsoft.com>
- Date: Fri, 23 May 2008 12:48:12 -0700
- To: "public-html@w3.org" <public-html@w3.org>, Ian Hickson <ian@hixie.ch>
- CC: Harley Rosnow <Harley.Rosnow@microsoft.com>, Chris Wilson <Chris.Wilson@microsoft.com>
Ian, Hope the weather's great down there in California. You may recall I posted about Operation Aborted last month [1], and I'm now looking at providing what we're calling the "full fix" for the problem. The trouble is, given our current architecture, we're just a little puzzled how to correctly implement the change. It seems quite straightforward at first thought, but if you consider the "delete" cases (removeChild on an ancestor), and the "replace" cases (outerHTML on an ancestor), we end up with a bit of a tricky situation. In our quest to find the "right" way to handle this error condition, I did a relatively quick deep-dive into section 8.2 of HTML5 to try to find if these cases are spec'd somewhere therein (I believe they should be), but came up empty-handed. Perhaps I was looking at an old copy of the spec (had it printed at the cost of a small forest--probably a bad idea), or I simply missed something obvious. I'd love your help trying to isolate the specific requirements from the current spec, or to help to define them if not specified. Travis Leithead - OM Program Manager - Internet Explorer [1] http://blogs.msdn.com/ie/archive/2008/04/23/what-happened-to-operation-aborted.aspx
Received on Friday, 23 May 2008 19:49:36 UTC