On Mar 11, 2009, at 01:53 , Doug Schepers wrote: > It seems riskier to bottleneck element parsing to one time-frozen > specification. I agree that implementations will update their > internal list of supported non-HTML elements and attributes > regardless of what HTML5 says, so it doesn't seem practical to > include any such list in the HTML5 spec. I think that this is a spec-engineering issue, and I'd like to make sure that it's not on the critical path for a resolution on SVG in HTML. In fact, it might be best if it didn't take any bandwidth away from this discussion. Since it becomes an issue when HTML5 becomes a Rec, I think we have a little bit of time to see this one coming. -- Robin Berjon - http://berjon.com/ Feel like hiring me? Go to http://robineko.com/Received on Wednesday, 11 March 2009 14:31:19 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:55:11 GMT