[Bug 12962] Typographic Conventions not implemented as portably as they could be

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12962

--- Comment #3 from Samuel Bronson <naesten@gmail.com> 2011-06-16 00:17:27 UTC ---
In particular, it would be better to at least not use the ":before" CSS
pseudo-element: not only is this unlikely to be supported by terminal-based
browsers (many of which don't seem to support CSS at all, though ELinks and
Emacs/W3 support CSS but not ":before"), it also leads to undesirable
copy/paste behavior. (In fact, this is how I noticed the use of ":before" in
the first place: Chrome wasn't rendering "&#9888;" (U+26A0 WARNING SIGN)
correctly, so I tried to paste it into PuTTY so I could ask unicode(1) about it
on my Debian box; I ended up having to pull up the Developer Tools.)

I've attached a screenshot of ELinks with document.colors.use_document_colors
set to 1, meaning "foreground colors only", and one with it set to 0, meaning
"no colors". (2, meaning "both foreground and background colors", was too
horrible to show here; the background was a dismal gray, and none of the
background colors used in this section of the spec was distinguishable from any
of the others in nay case.) I think the default setting was 0, but it might
have been 1.

So, anyway, things like "Warning:" and "Note:" should be included in the HTML,
and you should be careful not to depend on subtle color differences (or any
background color) for important distinctions. (Thankfully, it's easy to tell
the stuff that's supposed to be in boxes with distinct background colors apart
anyway.)

The most worrisome issue I'm seeing is that the examples are totally
indistinguishable from normal paragraphs in ELinks.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 16 June 2011 00:17:34 UTC