RE: Inline HTML

>> The reasoning behind us moving to include HTML more directly is that 
>> using <foreignObject><html xmlns=...>etc is pretty inconvenient, for 
>> something we'd like to make easier and more convenient.

> At least this defines some viewport, that can be used to put
> the XHTML in and it defines the language used roughly with a 
> namespace indication.

Yes, IF it would finally be supported by Microsoft. foreignObject seems to work quite amazingly well in Chrome, Firefox, and Safari: I don't know whether to hope for MS to come to their senses or die off. One or the other, please.

It seems to me extremely ambitious to nest in some brand new way. Compared to the other complexities involved in modern web coding, dealing with namespaces and constraints like this seems perfectly reasonable to me. If only browser vendors would support it. 

Max

__

Max Dunn
President
Silicon Publishing, Inc.

Received on Sunday, 17 November 2013 00:48:51 UTC