Web Technologies

From: Arthur Wiebe <webmaster@awiebe.com> Date: Fri, 11 Apr 2003 13:54:08 -0500 Message-ID: <3E970F50.4000202@awiebe.com> To: Ernest Cline <ernestcline@mindspring.com>, www-html@w3.org

Ernest Cline wrote:

>This is related to the <include> thread, but I am not proposing a new 
>element.  One of the problems that frustrates the use of <object> to 
>incorporate parts of a document as a separate (X)HTML file is the lack 
>of any guidance as to how it is supposed to be treated.  As a result, 
>it is impossible to get any consistent presentation.  For example, one 
>major browser by default always includes scrollbars, even if they are 
>not needed, unless some non-standard additions to HTML are used.  I 
>think that it would be extremely helpful if at the minimum, some 
>guidance, and hopefully some requirements were included in XHTML2 as to 
>the expected behavior of an (X)HTML file incorporated into another by 
>means of the <object> element.
>
>A proposed definition of the expected behavior follows:
>
>An HTML or XHTML file included via either the <object> element or the 
>src attribute MUST be treated as follows:
>
>The presentation of the file must be the same as if the (X)HTML code 
>contained in the <body> were contained in a pair of nested <div>'s in 
>the originating file. The outer <div> shall have the same presentation 
>properties as the as the element that the included file replaces in the 
>originating file, and the inner <div> shall have the same presentation 
>properies of the <body> of the included file.
>
>No styling or scripting defined in the originating file shall affect 
>the included file.
>
>No styling or scripting defined in the included file shall affect the 
>originating file.
>
>
>  
>
It sounds good execpt why can't styling or scripting afftect the 
included file? I think it should rather say this
Any styling or scripting defined in the included file shall affect the 
originating file.

-- 
Arthur Wiebe
Visit http://awiebe.com/ 

Web Technologies

Re: Object and (X)HTML