W3C home > Mailing lists > Public > www-html@w3.org > April 2003

Re: Object and New Insert Code Element

From: Etan Wexler <ewexler@stickdog.com>
Date: Thu, 10 Apr 2003 16:23:31 -0700
To: Arthur Wiebe <webmaster@awiebe.com>
Cc: www-html@w3.org
Message-id: <BABB490A.DF9%ewexler@stickdog.com>

Arthur Wiebe wrote to <mailto:www-html@w3.org> on 10 April 2003 in "Re:
Object and New Insert Code Element" (<mid:3E95AE4B.7030108@awiebe.com>):

> object takes the file and treats it like a movie or media file.

An 'object' element merely identifies a resource for embedding (and possibly
software to handle the reource). It is your user agent, faulty by your
measure (and by mine), that treats the resource like a movie or media file.

> It doesn't just simply insert the code[,]
> which would work a lot better.

I still do not know the details of your situation. I suspect that you are
trying to render a resource of type "application/xhtml+xml" as though it
were of type "text/plain". Such a plan is bogus. The correct behavior is to
respect the semantics and syntax identified by the media type name. Thus an
embedded XHTML resource should render in a manner similar to the manner in
which non-embedded XHTML renders.

A really good user agent would allow configuration by the user to treat all
XHTML like plain text. I spot two problems. The first is that your user
agent, Arthur, is demonstrably not really good, which is what prompted your
original message in this thread. The second problem is that when XHTML is
treated like plain text, embedding becomes impossible, thwarting you from
yet another angle. 

-- 
Etan Wexler <mailto:ewexler@stickdog.com>
Received on Thursday, 10 April 2003 19:25:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:55 GMT