Forum:Bad color match for DarkVector skin

It took me a number of tries before I finally looked very closely at the entry field for 'source file' on the Upload File page before I spotted that the filename was actually there, just very very hard to see. I suspect that it is a grayed-out version (ie 'field disabled') of a darker gray color.

I use the Firefox browser (3.6.12).

While I have your attention... While trying to get a source file entered there, I was annoyed that I could not simply paste a string in the field. Clicking on the text field brought up the "browse files" dialog. Why have a text entry field at all there, if you aren't going to allow direct entry? If you absolutely must forbid manual pathname entry, why not make it a non-entry element?

--Eirik Ratcatcher (talk) 19:03, 2 December 2010 (UTC)
 * Can you get a screenshot? I don't see any problem with CSS.  Also, for the second bit, blame your browser.  &lt;input type="file"&gt; behavior is not governed by the website but by the browser. -- 19:07, 2 December 2010 (UTC)


 * File:DarkVector Fail.jpg - there ya go. Enough UI to show it's DarkVector, and the input box, pretty much as it appears on my screen. --Eirik Ratcatcher (talk) 22:03, 2 December 2010 (UTC)
 * So the text is too white to see? That's odd...  Anyway, we haven't styled that box so if nothing else blame your browser.  We're looking at this (somebody styled it and it wasn't showing up for me), but the fact remains that Firefox is messing it up in part. -- 22:06, 2 December 2010 (UTC)


 * Perhaps Firefox IS messing it up in part. Would like to know which part in particular.  You know, reporting bugs.


 * I pulled just the form code out of both wowwiki and wowpedia, and the wowpedia code insisted I set an encoding on the file (chose: no-BOM). This resulted in a number of unicode characters being displayed between the legend ("source file") and the input box.  But only on wowpedia.  The characters are not obvious to me, but might well be raw linefeed (0x0A) characters that my editor didn't know what to do with. --Eirik Ratcatcher (talk) 23:06, 2 December 2010 (UTC)
 * We changed it so you should be able to see the file name now, let us know if that works. -- 23:09, 2 December 2010 (UTC)
 * Except for one flaw, that does make the text visible. The flaw?  Any non-trivial pathname gets truncated/hidden by the Browse button.
 * We observed this problem in an in-house web application, and (I presume with AJAX) modified the input field to "text followed by edit/remove links". This solution doesn't work without javascript, though. :(  Wish the field would just show "...Last/portion/of/path.ext".  --Eirik Ratcatcher (talk) 23:20, 2 December 2010 (UTC)
 * Still, the feedback that I have, in fact, entered a filename is helpful. --Eirik Ratcatcher (talk) 23:21, 2 December 2010 (UTC)