Open
Bug 1386100
Opened 7 years ago
Updated 3 days ago
"white-space: normal" style rule collapses newlines in textarea
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: marcausl, Unassigned)
References
Details
(Keywords: parity-chrome, parity-safari)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0 Build ID: 20170727114534 Steps to reproduce: visit https://support.tivo.com/CreateCaseFromSupport try to type in How May we Help You using the enter key to create more than one line of text Actual results: The enter key produces a space or nothing Expected results: Enter key should create new line.
Comment 1•7 years ago
|
||
Removing white-space:normal from CSS solve the issue, but I'm not sure if this is an expected behaviour. See also https://connect.microsoft.com/IE/feedback/details/818266/newline-n-problem-with-whitespace-nowrap-or-whitespace-normal-in-textarea
Component: Untriaged → Editor
Product: Firefox → Core
Comment 2•7 years ago
|
||
Chrome Canary and WebKit don't collapse newlines.
Summary: enter key does not create new line → "white-space: normal" style rule collapses newlines in textarea
Whiteboard: [parity-webkit][parity-chrome]
Updated•7 years ago
|
Component: Editor → Layout: Form Controls
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
status-firefox57:
--- → wontfix
status-firefox58:
--- → fix-optional
Comment 3•6 years ago
|
||
So, I think Firefox's behavior is correct on this in terms of relevant specs. But I can understand that probably no author actually wants to make <textarea> collapse whitespaces like this. One solution to this compat issue would probably be changing the HTML spec to make "white-space: pre-wrap" declaration "!important" so that author stylesheet cannot override the value of this property on <textarea>. This would make the spec match the behavior of Blink and WebKit without any further special-casing.
Comment 4•6 years ago
|
||
Filed HTML spec issue whatwg/html#3301 for this.
See Also: → https://github.com/whatwg/html/issues/3301
Comment 5•6 years ago
|
||
https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals
status-firefox59:
--- → ?
Comment 6•6 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome,
parity-safari
Whiteboard: [parity-webkit][parity-chrome]
Comment 7•2 years ago
|
||
This is causing issues on this form: https://sharoushi.o-sr.co.jp/contact
See Also: → https://webcompat.com/issues/100070
Updated•2 years ago
|
Webcompat Priority: --- → ?
Updated•2 years ago
|
Webcompat Priority: ? → P3
Updated•2 years ago
|
Severity: normal → S3
Comment 8•3 days ago
|
||
The problem no longer reproduces on sharoushi.o-sr.co.jp, and we're unaware of other sites where this is a problem, so let's unset the webcompat priority for now.
Webcompat Priority: P3 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•