Closed Bug 1153654 Opened 10 years ago Closed 10 years ago

In Firefox 37, textarea fields are too narrow and are no longer resizable

Categories

(Core :: CSS Parsing and Computation, defect)

37 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: DavidCharlap, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20150320202338 Steps to reproduce: Visit this page: http://submit.macintouch.com/ using Firefox 37 Note the size of the "Message" multi-line text-entry field. Try to resize it using the "thumb" in the lower-left corner. Actual results: The field is extremely narrow (about 30 columns, even though the HTML indicates that it should be 60 characters wide. It can only be resized vertically. There is no way to make it wider. This bug first appeared in Firefox 37.0, and is still present in 37.0.1 Expected results: Using Firefox 36.0.4 and earlier versions, the text field is 63 characters wide (slightly wider than requested, but that's OK), and it can be resized both horizontally and vertically. This is the behavior I expect to see.
Just to clarify my report a bit more. The field I'm calling a "multi-line text-entry" field is a "textarea" in the HTML. Also note that although I'm reporting this for Mac OS X, I have seen the exact same behavior on Windows 7. It is therefore probably affecting all platforms.
Summary: In Firefox 37, text entry fields are too small and are no longer resizable → In Firefox 37, textarea fields are too narrow and are no longer resizable
problem is page css http://submit.macintouch.com/css/form.css line 40 textarea { max-width: 40; min-width: 20em; font-size: 1.0em; } on Firefox37, max-width is treated as 40px in accordance with spec (unit less length is fixed by bug 774122 on Quirks mode ) So this bug is invalid.
Component: Untriaged → CSS Parsing and Computation
Product: Firefox → Core
Looks like the CSS mentioend in comment 2 has been changed to "40em" instead of "40".
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.