Closed Bug 28806 Opened 25 years ago Closed 25 years ago

<font size=small> gives large text

Categories

(Core :: Layout, defect, P3)

Product:
Core
Component:
Layout
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: ken.horn, Assigned: pierre)

References

(
URL
)

Details

Example site use: http://www.sun.com/workshop/tools4dotcom/ffjce-012600.html <html><body> MyProduct<font size="small">TM</font> This gives a LARGE tm. The above URL also uses <sup> to nest the font tag, but this makes no difference to the size.
There is no documented use of "small" for <FONT SIZE=...> http://developer.netscape.com/docs/manuals/htmlguid/tags6.htm#1288938 http://www.w3.org/TR/html401/present/graphics.html#h-15.2.2 (deprecated) However, note that Nav4.x (and IE3.0 [don't have 4.0]) will treat *any* text value in the SIZE attribute as equivalent to <FONT SIZE="1"> <html><body><basefont size='3'> MyProduct <font size="small">TM</font> <br> MyProduct <font size="large">TM</font> <br> MyProduct <font size="foobar">TM</font> <br> MyProduct <font size="1">TM</font> <br> MyProduct <font size="2">TM</font> <br> MyProduct <font size="3">TM</font> <br> MyProduct <font size="4">TM</font> <br> MyProduct <font size="5">TM</font> <br> MyProduct <font size="6">TM</font> <br> MyProduct <font size="7">TM</font> <br> </body></html> I wouldn't really view this as a candidate for 'bugwards' compatibility. However, on 2000022108 win95, mozilla is treating this as equivalent to <FONT SIZE="7"> which is not the right thing to do (better to just ignore it if it isn't a valid integer).
agreed.
I'm going to CONFIRM this to move it up to rickg/harishd's to-do list. I believe the bug here is that an invalid attribute value for <FONT SIZE='value'> should be a no-op. [Although this may be Style System, and not Parser where the fix must be implemented].
Status: UNCONFIRMED → NEW
Ever confirmed: true
It's true that Nav4x treats size=small, size=large and size=foobar as size=1, IE treats them as size=3. Also note that the parser's job is NOT to resolve these kinds of issues. This is clearly a style problem, not one of consumption or producing a wellformed document (which the parser is responsible for). Over to pierre for a look, to see how this works against his new fontsizing code.
Assignee: rickg → pierre
Assigning to Waqar: 1/3 of Pierre's NEW bugs to help reduce his doomage factor
Assignee: pierre → waqar
Reassigned back to me these bugs that shouldn't have left my list.
Assignee: waqar → pierre
It was fixed last week, along with bug 32063.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed in the July 6th build.
Status: RESOLVED → VERIFIED
SPAM. HTML Element component deprecated, changing component to Layout. See bug 88132 for details.
Component: HTML Element → Layout
You need to log in before you can comment on or make changes to this bug.