Page 1 of 1 [ 7 posts ] 

AlexGrim
Butterfly
Butterfly

User avatar

Joined: 25 Jan 2009
Age: 46
Gender: Male
Posts: 14
Location: Transgression

26 Jan 2009, 10:30 pm

In your text boxes and text areas the background is white; conversely, your text is white also. This causes the person typing to be unable to see what they are typing. I noticed that when clicking the mouse, during the onMouseDown event, the text changes to black, rendering it readable. If you edit your CSS or javascript to set the normal font colour to a darker colour, this problem will be no more. Because the text changes colour during the onMouseDown event, i think that it is safe to conclude that the problem is in the javascript, and not the CSS; but that may not necessarily be true.



0_equals_true
Veteran
Veteran

User avatar

Joined: 5 Apr 2007
Age: 44
Gender: Male
Posts: 11,038
Location: London

27 Jan 2009, 5:03 am

How are you obtaining focus with tab?

Can you repeat the exact step you made to repeat this behaviour, plus tell me you browser and version. Also disable JavaScript, refresh and repeat the process.

If this were a widespread problem there would be a lot more people complaining about it. However it might be a browser specific quirks, they may or may or may not be addressable if it doesn't mess everything up for other people The forum has bigger problem than this and they haven't been fixed yet, so i wouldn't hold out too much hope.



AlexGrim
Butterfly
Butterfly

User avatar

Joined: 25 Jan 2009
Age: 46
Gender: Male
Posts: 14
Location: Transgression

27 Jan 2009, 5:15 am

To repeat, simply hit the 'reply' button, and whala; you cannot read what you are typing. Refreshing browser and cookies made no difference. I am using Firefox 3.x on Fedora Linux.



0_equals_true
Veteran
Veteran

User avatar

Joined: 5 Apr 2007
Age: 44
Gender: Male
Posts: 11,038
Location: London

27 Jan 2009, 6:16 am

Ok I haven't been able to replicate because I doesn't get the focus automatically anyway. I don’t have fedora.

I think it might be due to the fact that the css is riddled with errors namely color: with nothing after it is not valid css.

Again don't hold out hope about getting this fixed soon. Really firefox should handle it, mine does. You can explicitly set user styles to correct this. Default font should always be black. Sometimes in the olden day before css took over browser used to vary text colour depending what the bgcolor attribute of the body tag anymore. This not really a standard complaint.

You should have to explicitly set the color, however having the colour there with nothing after it is obviously going to cause syntax errors.

Like so

body{color:black!important}



AlexGrim
Butterfly
Butterfly

User avatar

Joined: 25 Jan 2009
Age: 46
Gender: Male
Posts: 14
Location: Transgression

27 Jan 2009, 6:27 am

Yes, well the problem is that i use a dark theme for my desktop ( http://LinuxIntro.com/1.png ); the background is black, and the text is white, so i tell firefox NOT to use system themes, and use the website's instead. I do not like to override the web author's intended colours, as it kind of takes away from each designer's style. I will just wait around for it to be fixed.

Thanx



0_equals_true
Veteran
Veteran

User avatar

Joined: 5 Apr 2007
Age: 44
Gender: Male
Posts: 11,038
Location: London

27 Jan 2009, 8:05 pm

Ah that will be the reason. Um they won't necessarily make fixes for that per say. Yes they can explicitly set the text to be black by but there no reason to, it is not invalid not to.

In your Firefox profile /chrome directory try putting the following in userContent.css

Code:
input[type="text"], textarea {
   color: black  /* or red  or any color */ !important;
}


If a site has explicitly set input styling say in div it will not mess up their styling. You are only changing the input styling. There is not styling there to mess up! Input styling so rare especially the colour (guaranteed to wind people up). If a site has explicitly set input styling say with and id it will NOT mess up their styling. It is pretty likely there will use an id because css3 is still not taken hold completely. You can even drop the !important part. Seriously userContent.css is pretty useful check it:

http://cssing.blogspot.com/2004/08/my-o ... weaks.html
http://www.gozer.org/mozilla/ad_blocking/
google...

Nobody should have to put up with things they really don’t want.

If you only want this to be applied to WP (I don’t why when it is so useful), you can do this:

Code:
@-moz-document domain(wrongplanet.net){

input[type="text"], textarea {
   color: black  /* or red  or any color */ !important;
}

}



AlexGrim
Butterfly
Butterfly

User avatar

Joined: 25 Jan 2009
Age: 46
Gender: Male
Posts: 14
Location: Transgression

27 Jan 2009, 10:57 pm

Ahhh, nice work around; i may give that a shot. It is just a pet peve of mine when people do not explicitly style all textual elements. If i do not have something explicitly set on one of my websites, then it is only because i forgot.

Thanx