问题
Is there any way that I could display HTML tags without parsing? Tags like XMP worked before perfectly but now it's replaced with PRE that isn't so cool. Take a look at this example:
//This used to NOT PARSE HTML even if you used standard < and >.
Link
//New PRE tag requires < and > as replacement for < and >.
<a href="http://example.com">Link</A>
What I'm looking for is equivalent of old XMP tag. New PRE tag will parse code.
回答1:
You can use a script element with its type set to denote plain text, and set its display property to block. This only affects the parsing behavior: no markup (tags or entity or character references) is recognized, except for the end tag of the element itself . (So it is not quite the same as xmp, where the recognized tag is .) You can separately make white space handling similar to that of xmp and pre and/or set the font the monospace as in those elements by default.
Example:
script {
display: block;
}
Then within document body:
é
Tested on newest versions of IE, Chrome, Firefox, Opera. Didn’t work in IE 8 and IE 7 emulation on IE 9, but that’s probably a bug in the emulation.
However, I don’t see why you would use this instead of xmp, which hasn’t stopped working. It’s not in the specs, but if you are worried about that, you should have always been worried. Mentioned in HTML 2.0 (the first HTML spec ever) as avoidable, it was deprecated in HTML 3.2 and completely removed in HTML 4.0 (long ago: in 1997).
The xmp is making a comeback rather than dying. The W3C HTML5 (characterized as the current HTML specification by W3C staff) declares xmp as obsolete and non-conforming, but it also imposes a requirement on browsers: “User agents must treat xmp elements in a manner equivalent to pre elements in terms of semantics and for purposes of rendering. (The parser has special behavior for this element though.)” The old parsing behavior is thus not explicitly required, but clearly implied.
回答2:
Hey Guys I personally think using the
tags only works in Dream Weaver and
the tag
never stopped working unless you put in it works fine. Using makes it so that others can edit your code on the website or the page so I recommend that the tag is still used and that that tag still lives on.回答3:
The modern way is to use textarea with (boolean) attribute readonly. You could use XMP, but that is deprecated, so it may eventually stop being supported.
example:
This is some text
回答4:
There isn't.
In theory you could use a CDATA block, but no browser supports that in text/html mode.
Use character references.
回答5:
If you want to be more complex, another way is to create a custom tag using jQuery. For this example, I used .
$('noparse').each(function(){
if($(this).attr('tagchecked') != 'true'){ //checks if already changed tag
$(this).text($(this).html()).attr('tagchecked', 'true'); //makes the html into plaintext
}
});
JSFiddle here
回答6:
And then... a few years go by, I have the same problem while converting my blog from wordpress to a vuejs spa backed by lambda and dynamodb.
And the answer is; at least in my situation. Escape the entity.
< becomes <
> becomes >
etc. etc.
Hope this helps.
回答7:
I suggest using the html iframe tag and put the text you like to display in the src attribute. you only have to url or base64 encode it first.
example (urlencoded):
example (base64):
Result displayed as:
""
回答8:
Technically you could use , but it would require that there be no tag in the code you are trying to show. It'd just easier to escape the <.>
回答9:
Well, one way would be to use jQuery. the jQuery .text() method will encode special characters. And the original un-encoded text will remain if you view source.
var t = $('#text'); t.html(t.text());
来源:https://stackoverflow.com/questions/11673978/is-there-a-html-css-way-to-display-html-tags-without-parsing