Closed
Bug 765646
Opened 12 years ago
Closed 12 years ago
placeholder in focused input is indistinguishable from typed text
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(firefox15-)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox15 | - | --- |
People
(Reporter: karlt, Unassigned)
References
()
Details
(Keywords: regression)
STR:
1. Load http://www.mozilla.org/contact/
2. Click in search box
Actual results:
Grey placeholder changes to black text as if "Search" had been entered.
Expected results:
Some way to distinguish between placeholder and text to be submitted.
Comment 1•12 years ago
|
||
The site is explicitly styling focused inputs with a dark text color (#333, not black, but it's hard to tell the difference).
Updated•12 years ago
|
Component: DOM: Core & HTML → www.mozilla.org
Product: Core → Websites
QA Contact: general → www-mozilla-org
Version: 15 Branch → unspecified
Updated•12 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Reporter | ||
Comment 2•12 years ago
|
||
Is it expected that the "color" property affects the placeholder?
Comment 3•12 years ago
|
||
(In reply to Karl Tomlinson (:karlt) from comment #2)
> Is it expected that the "color" property affects the placeholder?
Yes. For instance, if an input field was styled with gray background and red text, leaving the placeholder gray would be worse than making it red as well. If you specifically want to change the color of the placeholder, you need to use :-moz-placeholder.
Comment 4•12 years ago
|
||
What the.. i created this ticket, and i seem to have no reply in it, or access to it, as im not its author anymore.
I typed:
"1. Load http://www.mozilla.org/contact/
2. Click in search box"
And added the version and rest of the details. Why was i changed as the reporter/author o-O
Comment 5•12 years ago
|
||
This is a website issue.
Fixed with r106451.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Reporter | ||
Comment 6•12 years ago
|
||
Regressions are marked as blockers.
I assume the website adjustment does not depend on changes in bug 673873
(or there would be feature testing to get desired behavior on older versions).
opacity should solve these issues for other sites (cf. bug 673873 comment 48 et al.)
Is there a reason why this Core bug was not left open to track that?
(In reply to Radulescu Dragos-Valentin from comment #4)
> What the.. i created this ticket,
I think you are remembering bug 758996.
I CC'd you on this bug because it is related, and I thought you might be interested.
Updated•12 years ago
|
Component: www.mozilla.org → General
Product: Websites → Firefox
QA Contact: www-mozilla-org → general
Updated•12 years ago
|
Updated•12 years ago
|
Component: General → www.mozilla.org
Product: Firefox → Websites
QA Contact: general → www-mozilla-org
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Karl Tomlinson (:karlt) from comment #6)
> opacity should solve these issues for other sites (cf. bug 673873 comment 48
> et al.)
Bug 556145 covers that.
Assignee | ||
Updated•12 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Comment 8•12 years ago
|
||
bug 556145 should fix this bug on the Gecko side.
You need to log in
before you can comment on or make changes to this bug.
Description
•