Closed
Bug 734337
Opened 12 years ago
Closed 7 years ago
input { color: blue; } should not override color of placeholder text
Categories
(Core :: Layout: Form Controls, defect)
Core
Layout: Form Controls
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mathias, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.66 Safari/535.11 Steps to reproduce: The placeholder text will display in hot pink, but it shouldn’t: <style>input { color: hotpink; }</style> <input placeholder=foo> Demo: https://tinker.io/be2f2 No other browser does this. Actual results: The placeholder text displays in hot pink. Expected results: The placeholder text color shouldn’t change when `input { color: … }` is set.
Comment 1•12 years ago
|
||
Yes, indeed. But this is known. When changing color, authors should change the placeholder color. Though, we might end up with better default but we need to have ::-moz-placeholder instead of :-moz-placeholder for that.
OS: Mac OS X → All
Hardware: x86 → All
Comment 2•12 years ago
|
||
I thought this was a purposeful decision, in fact, and one of the reasons we had done the pseudo-class thing.
Comment 3•12 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #2) > I thought this was a purposeful decision, in fact, and one of the reasons we > had done the pseudo-class thing. Yes, IIRC that was to force authors to think about the placeholder color because grey isn't always a good idea. Though, with a pseudo-element, we could use opacity which might fix that issue, I guess.
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Mounir Lamouri (:volkmar) (:mounir) from comment #1) > Yes, indeed. But this is known. When changing color, authors should change > the placeholder color. Though, we might end up with better default but we > need to have ::-moz-placeholder instead of :-moz-placeholder for that. The problem with the current situation is that once `:-moz-placeholder` becomes `:placeholder` (or whatever the standardized version will be), authors that styled `<input>` color will have to go back and edit their stylesheets just to make the placeholder text look distinct again. I don’t think this is very useful.
Comment 5•7 years ago
|
||
Yesterday I opened a new Bug with description of the issue and screenshots. Bug 1357674 without knowing this one. It creates a Web Compat issue. https://webcompat.com/issues/5895 Which way should I dup. old dup of the new (there's a bit more context in the new one). new dup of the old. hmm… let's try to DUP this into the new one.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Comment 6•7 years ago
|
||
Following discussion on Bug 1357674 with Boris (Thanks!). Let's undup and resolves this as WORKSFORME.
Updated•7 years ago
|
Resolution: DUPLICATE → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•