Closed Bug 373914 Opened 18 years ago Closed 18 years ago

CSS relative font-size in Textarea renders incorrectly

Categories

(Core :: Layout, defect)

1.8 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: ritalientje, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9 When specifying the font-size in CSS for the Body tag font-size will render incorrectly in a Textarea. When declaring the font-family for the Textarea font-size renders correctly. Reproducible: Always Steps to Reproduce: 1. Create basic HTML page styled with CSS 2. Style the Body tag with any font-family and font-size of, for instance, 80% 3. Create a Form with a Textarea and for instance text input field 4. View result 5. To fix the bug, add additional font-family property in CSS for selector Textarea
Version: unspecified → 1.5.0.x Branch
Component: Form Manager → Layout
Product: Firefox → Core
QA Contact: form.manager → layout
Version: 1.5.0.x Branch → 1.8 Branch
This behavior is intentional; every other browser acts exactly the same way.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
The page in development and a subsequent testpage to recreate this behaviour was tested on all major browsers on Windows, Linux and Mac. This behaviour was only encountered in Firefox during testing. Why would this be intentional, what would be the benefit of unreadable text in a textarea? (In this case the font-size was set to 80% from base at Medium setting and rendered unreadable to users during testing.) And why would only the text in a textarea be differently rendered within the body, or even within a form? And why would adding a font-family to just the textarea selector render it as intended?
<body style="font-size: 25%"> <textarea>Doesn't shrink</textarea>Shrinks Works exactly the same in Fx and IE. Are you doing something different?
You need to log in before you can comment on or make changes to this bug.