ANYTHING surrounded by the < & > delimiters will be parsed by a browser as renderable HTML code.

Try it for yourself.
put <a_tag_i_made_up> A made up tag </a_tag_i_made_up> into a page and see what happens.

I don't think you understand what I'm trying to say. Even if I put: <pre><div class="code">this is code with no delimiters</div></pre>, anything after that isn't part of the P element.

So just for clarification let's say I have:

<p>
<pre><div class="code">this is code with no delimiters</div></pre>
whatever I write here is no longer part of p. So the ending div or ending pre must be stopping the p

Sure, but WHY do you need the div inside the<pre> element?

I don't necessarily, but that unfortunately doesn't solve the problem.

Do we get a link that demonstrates the problem? Because I'm obviously missing something here.

Check out the latest blog entry under the picture of the bear: http://bit.ly/72eXhZ

And the problem is??

Originally Posted by chrishirst

And the problem is??

Lol, look at the text size of something before the code, and then after.

I cannot see any difference at all.

Firefox, Seamonkey, IE8, Opera.

The FF DOM Inspector shows no problem at all with node nesting.

Have you cleared your browser cache?

In Firefox:



In Safari:




And in Google Chrome:

Very odd?
yet on my machine there is absolutely no difference, I've even taken a selection from a screenshot and overlayed the "and" onto "command" and they match exactly.

That's so weird. Hmm, maybe it's a Mac thing? I'll have to test it out on a few other platforms.

I still have not figured out a way to resolve this. Is there anything else that I could use instead of <pre> inside of the <p>? I've tried using <code>, which works great, but unfortunately my text box is only around each line and not around the entire block of code.

did you test it on other platforms besides mac?

Yes, look 3 posts above yours..

You can see a minor difference in IE, but a more drastic difference on Firefox & Safari.