Comment #35 on issue 1334 by beingzoe: Auto-filled input text box yellow
background highlight cannot be turned off!
http://code.google.com/p/chromium/issues/detail?id=1334
All the focus is on the background-color but input:-webkit-autofill only
styles the
background. In my case I was using nearly the same color text in the input
fields as
the pseudo-class rendering the 'autofilled text' literally invisible.
But this was easy enough to fix with:
input:-webkit-autofill {
color: #2a2a2a !important; /*important not necessary but if they
think so
;)*/
}
While it isn't ideal for most folks in my case it ended up looking like
part of my
design. And while I sympathize with everyone wanting to control that
feature, I
understand the theoretical argument from Google that allowing that to be
changed
would remove consistency in the visitor experience with the browser (not
your
website). If it happens on all websites then visitors aren't going to freak
out when
the text box turns yellow, quite the contrary they'll know exactly what is
going on.
However, considering sites using background images in the inputs that
argument simply
doesn't hold up. If the browser feature breaks the design of the very sites
it is
supposedly designed to render and in this case enhance, then it is failing.
It seems a ridiculous oversight in the webkit useragent stylesheet, if
insistent on
enforcing !important on the pseudo-class, to not also change the text color
as well.
That said, I agree with several comments posted here:
* The web development community would never shut up if it was IE doing this.
* If this doesn't happen in Safari why is it WontFix for something that
doesn't seem
to need fixed from the upstream source (unless Safari is changing it).
* Why not do something around and on top of the field that doesn't
interfere with
it's original appearance but accomplishes the same effect?
* Adding even one line of markup/script/code to deal with the browser seems
wholly
ridiculous and I expect more from Google than from Microsoft
We can only wish that WontFix didn't mean "won't" and instead meant "wont"
is in, "in
the habit of fixing such ridiculous but obviously annoying and potentially
disorienting features that were intended to improve the user experience, as
opposed
to discolor them that we aren't even going to list it as an accepted bug
because it
so embarrassing that we don't want to admit it publicly but will have fixed
in the
next release." Because to the average visitor it makes the website look bad
when the
page appears messed up or confusing, not the browser.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
