J
Jukka K. Korpela
brucie said:"Rendering of font style elements depends on the user agent. The
following is an informative description only."
That's one of the many obscurities in the specification. If you take it
literally, then some elements lack _all_ definitions. There are just
"informative descriptions" - and a browser could well render <big> as
extra extra small text, or make the text blink just because of the
<big> markup, or make a big noise. If we take the reasonable approach,
<big> _means_ (stands for) big font, and what depends on the browser is
_how_ big (how much bigger) it is rendered and whether the browser is
able to render the text bigger at all - i.e., whether it can implement
the meaning of the markup. Similar considerations apply to said:thats what i said.
Not quite. You said "it doesn't necessarily mean 'underline'". What I
wrote says that <u> always means 'underline', stands for 'underline',
but browsers might fail to implement this meaning.
It's like a teacher telling the students to underline some statement in
a textbook. Even if some students refuse to do that, perhaps to protect
the integrity of their books, or because they lack pencils and pens,
the teacher's instruction still _means_ 'underline'.