Re: <iframe doc="">

>>> If you put text/html into an <object> element (which is what we're
>>> suggesting with @doc), then it acts just like a frame.
>>
>> An iframe is not a frame. and iframe is not an object.
>
> What Adam and Maciej and I are telling you is that in at least Gecko 
> and Webkit they _are_ in fact the same thing, for purposes of HTML 
> rendering.  As in, the same exact code is used to implement HTML
rendering in all three.

OK, as for difference between <iframe> and <object>
(maybe somehow except if standard has grand exception if object @data 
is html)
what do these look like in whatever DOM inspector?

All efforts in <iframe> are to somehow how make it look like and act 
sort of like an object by limiting access using some iframe 
attributes. At least in Ff and in IE and everywhere else I hope the 
<iframe> and its content is actually in the same DOM as the parent 
document. We call it a nested context and build wals around it with 
sandbox attributes.
For <object> it is a real disticnt context. Its content should not 
show up in the inspector unless special case for html in object (I 
hope not).
For object (most pure) the content should not reside in the host DOM. 
The <object> is a distinct object context with limited connections to 
the host DOM. The host DOM can never (most purely) see inside the 
object, and the object can't see out, except by special DOM and 
network interfaces. For now, the <object> interfaces are defined by 
NAPI and by MS with NAPI apparently workable everywhere. I may be 
behind in my reading but this NAPI or MS object api have literally 
nothing to do with <iframe> that I can figure, but they have 
everything to do with <embed> and <object>.

Thanks and Best Regards,
Joe

Received on Sunday, 24 January 2010 20:38:13 UTC