- From: Daniel <tdaniel@adetti.net>
- Date: Tue, 3 Dec 2002 11:14:53 -0600
- To: <www-html@w3.org>
I'd say the main problem with this is that it would have CSS trampling on HTML's territory - it would mean CSS would have the power to change the MEANING of the HTML code. Whatever code existed inside the 'display: escaped' section would not really be code, but content. That's a pretty big trampling. Also, imagine what happens if someone has CSS disabled! Some browser support a <XMP> tag that does what you're talking about. I strongly recommend against using it, as it is non-Standard, browser support is spotty (as it should be for non-Standard code) and once again imagine what happens on a non-supporting browser, and IMHO it violates the spirit of HTML code. There are a number of tools out there that can translate HTML code into escaped characters. For example, I do most of my coding in an editor called jEdit (www.jedit.org) that has a plug-in that does this for me. I believe this is the prefered method of doing what you want to accomplish. My two cents, T. Daniel ----- Original Message ----- From: "Wingnut" <wingnut@winternet.com> To: <www-html@w3.org> Sent: Tuesday, December 03, 2002 10:41 AM Subject: escaping escaping > > Hello! Can we chew on the possibility of using CSS's... > > style='display: escaped;' > > ... where a styled-as-such elements' contents would hit the browser > escaped (not rendered), as in HTML source text? I probably have my > terms screwed up, but you understand. :) I am looking for a > container-tag or method to display html source without manually or > dynamically escaping the lt's, gt's, quotes, amps, etc... during > authoring. display: escaped; sounded rather interesting so I thought > I'd throw it to the wolves for consumption. :) I'm still looking-into > SOURCE, CODE, PRE, SAMP, etc. All comments welcome. If > topic-wandering, email directly to me as wanted. > > Best regards! > Uncle Wingnut > wingnut@winternet.com > >
Received on Tuesday, 3 December 2002 12:15:20 UTC