Re: Definition of a replaced element

> Fair enough - me being lazy and trying to do everything in one file.  
> The example I should have given is this:

The use of one file is of the essence of the issue.  <object>, when 
successful, is the classic example of a replaced element in HTML.  We
are talking aout <svg:svg> elements, which are not defined by XHTML.

If the document processor didn't know about SVG, it would have applied
the CSS to the foreign namespace content, so it is not inevitable that
a conforming user agent will treat <svg:svg> as replaced.

Where the user agent is aware of something like <svg:svg>, I think
it should be up to the embedded namespace standard to specify if and
when it is treated as a replaced element for the purposes of CSS in the
containing document.  (I suppose the parent namespace specification could
also specify that foreign namespaces, in general, should be treated as
replaced, but that wouldn't be appropriate for XHTML.)

I believe the real problem here is that the commercial SVG community
really teats both CSS and mixed namespaces as political impositions and
have had to be dragged kicking and screaming into implementing consitent
interpration of CSS and have put mixed namespace documents at a priority
at which they may never get considered.  Neither of these features is
needed when you are creating a product to compete with Flash or a mobile
phone games environment.

Received on Thursday, 4 January 2007 07:40:51 UTC