The particular font that the browser rendered in response to the percent mark was identical to the one it rendered in normal use in the posting box.

But why wasn't that being overridden by monospace in buffista.css? And was it indented?

% percent

carat

plaintext

In my example above, the percent line matches the plaintext line, and the carat line is indented and monospace.

According to Chrome's debugger, the line "percent" only has paragraph tags, no "blockquote" anywhere.

"carat" is wrapped in "cite" and the styling is showing up correctly.

You have a space in front of the % sign, so that's why it's not encoding. Those quickedits need to be first on the line.

% percent (blockquote)

greater than (cite)

I still don't see anything with the %.

Drilling down in chrome, I get a CSS match for buffistas.css cite{} on the cite line that sets it to monospace, but no equivalent match on the blockquote line. The only match I get on buffista.css for the blockquote line is the body{} block.

Hmm. It seems Chrome isn't correctly refreshing my sytlesheet or something, because the lines I'm seeing in the debugger do not match the ones I see if I go to [link] .

Okay, here's my inheritance when I delete personal customisation. This is the computed style:

color: #000000;
display: block;
font: normal normal 400 16px/normal Consolas;
height: 19px;
margin: 2px 64px;
padding: 0px;
text-align: left;
width: 669px;

And here is the tree that shows how that came about: [link]

Why is it not triggering buffista.css lines 185 and 190 for everyone? Is it being overridden by the user agent stylesheet? You can see that mine's being overwritten, which is my expectation...naive as I am.

For me, it was totally a refreshing thing. I changed the background color on my own personal stylesheet and it didn't work either. Then I shift-refreshed about 3 times, and suddenly got the new color AND the correct behavior on the blockquote. The CSS must have been cached, and Chrome wasn't checking correctly for a new version or something.

Working for me correctly in Firefox, too.

Everybody try shift-refreshing a few times!