- From: Braden N. McDaniel <braden@shadow.net>
- Date: Mon, 3 Aug 1998 12:41:55 -0700
- To: "'David Perrell'" <davidp@earthlink.net>, "'HTML'" <www-html@w3.org>, "'Style'" <www-style@w3.org>
> -----Original Message----- > From: www-style-request@w3.org [mailto:www-style-request@w3.org]On > Behalf Of David Perrell > Sent: Monday, August 03, 1998 9:37 AM > To: 'HTML'; 'Style' > Subject: Re: OBJECT, inheritance, and rendering > > > > Braden N. McDaniel wrote: > > >Note: That URL refers to the Proposed Recommendation. The > matching section > >in the Recommendation can be found here: > > > > <http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.5> > > > Thanks for reminding me my bookmarks need updating. > > >I still perceive the problem I mentioned with monochromatic > inclusions > (such > >as text files). Section 13.5 of the HTML spec appears to > speak only to the > >inclusion of other HTML files. Besides, I maintain that it > would be a Good > >Idea to treat monochromatic inclusions uniformly where color > is concerned. > > > Text inclusions via OBJECT are generally useless without standardized > rendering. What treatment would be most useful to authors? > Should a text > OBJECT be the client-side equivalent of a server-side include > -- a means to > assemble content fragments at display time? I don't like that idea. I'm not averse to the notion of a client-side inclusion mechanism, but I don't think it should be tacked onto OBJECT's functionality. AFAICT, every other media type OBJECT can include has a notion of residing in its own box--why should text be different? I think it would be most useful if a plain text file were rendered in its own box, as pre-formatted text (that, after all, is how a browser will display a plain text file if it is brought up in the main window). Braden
Received on Monday, 3 August 1998 15:34:45 UTC