TEXTAREA does not follow HTML size/font/paragraph rules

RESOLVED INVALID

Status

()

Core
Layout
P3
normal
RESOLVED INVALID
16 years ago
15 years ago

People

(Reporter: Mateo, Assigned: kinmoz)

Tracking

Trunk
Future
x86
Windows 98
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc2) Gecko/20020510
BuildID:    2002051006

- If font is not defined, Mozilla shows Verdana for "Input Type" fields while it
shows Courier for "textareas".  This makes no sense.

- When css defines <p> it affects form elements inside the paragraph, but not
the textarea.

- Curiosity: If css defines the size of the text in the form field, then both
are shown correct size.


Reproducible: Always
Steps to Reproduce:
Take a look at all the 3 attached files.  They clearly explain how to reproduce
and what is going on.  Spent quite some time on that.

Ive seen similar bug reports, but either they were off track, or not exactly the
same thing (textarea size).  This might be the real problem of them, though.
(Reporter)

Comment 1

16 years ago
Created attachment 84869 [details]
Font is not defined, it is showing Verdana and Courier (different fonts!!!)
(Reporter)

Comment 2

16 years ago
Created attachment 84870 [details]
Input type follows <P> rules, textarea does not.
(Reporter)

Comment 3

16 years ago
Created attachment 84871 [details]
font size defines textarea, then it shows same as input

Comment 4

16 years ago
Changing QA contact to Amar
QA Contact: petersen → amar

Comment 5

16 years ago
Changing QA contact to petersen
QA Contact: amar → petersen

Comment 6

16 years ago
Confirming in the OS X June 2nd build (2002-06-02-05 1.0.0).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
-> Rods
Assignee: attinasi → rods
Target Milestone: --- → Future

Comment 8

16 years ago
-->
Assignee: rods → kin
This behavior is intentional -- see bug 96414
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.