W3C home > Mailing lists > Public > www-html@w3.org > December 2008

Re: Replaceable element for parameterising pages (was: Proposal for small enhancement)

From: Sorin Schwimmer <sxn02@yahoo.com>
Date: Fri, 5 Dec 2008 09:15:36 -0800 (PST)
To: www-html@w3.org
Message-ID: <601827.63615.qm@web56008.mail.re3.yahoo.com>

Thanks for your answers.

Because of a typo (old habits die hard), the example file myfile.css should have been myfile.ccs, although the actual name should be irrelevant.

David:
1. &nbsp; is replacing one character; I'm talking about more then one, including html code that need to be inserted before it is interpreted by the browser
2. I'm not sure what you mean by "redirection" - is it loading another page instead of this one? If so, it does not serve my purpose. I want to add some on-the-fly generated code (be it text content, HTML code, JS code, even SVG code if embedded in HTML), not to replace the whole page.
3. The id attribute has nothing to do with the usual semantic for an id attribute. Remember that the <r> element dissapears, by being replaced with the invoked content, and so will dissapear it's id attribute. It is the same like using #define in C/C++ - whatever name was used there is replaced with the actual value by the preprocessor, and the compiler never sees it.
4. "tag", "element" - yeah, you're right, I'm a bit loose here.

Andrei:
1. CSS has indeed "content". Many voices are against it, and I subscribe to that, as CSS is about style (presentation), and not content
2. Even so, "content" is related to an HTML element (p, div, span...) and won't allow parsing and interpreting HTML code.

The aim of my proposal is to have a mechanism (under UA management) in which the <r>'s are searched, if found, replaced, and afterward the new text is processed normaly.

Try to accomplish what I'm describing with existing tools (see example in my first posting). At client side there is only JS, not an easy approach for my stated goal.

Regards,
Sorin Schwimmer


      
Received on Friday, 5 December 2008 17:16:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 5 December 2008 17:16:17 GMT