- Jun 24, 2001
- 24,195
- 856
- 126
OK, with issues like this in the 9x days, you always turned HW acceleration down in the graphics options, and I'm thinking that this issues may be related, hence, this forum, but this has been happening on every Windows Vista/7 computer I used and in most browsers. I first noticed in in the fields for YouTube comments but soon noticed it on sites everywhere, including this forum. I believe it has something to do with the way new browsers handle text fields, like they all decided to update and use one with glitchy cursor/insertion point code.
Basically, sometimes is stops blinking and the only way to find it is to type something or reset it with your mouse but it remains invisible. Sometimes clicking out of the text field of hovering your mouse pointer over a different text field will trigger it to start blinking but it will usually stop again when you move back to the field you needed it in.
In decades of computing, a functional cursor/insertion point has always been something I could count on. In recent months, it's been F'd up royally. Whoever is responsible should be ashamed. I don't know if a change in graphics drivers (most of the systems I use are nVidia), an updated API/library in Windows, or something with FF4/IE9, but I didn't notice it until several months ago and it has been happening to me on a daily basis ever since (both PCs at home and the PC at work). I didn't say anything at first because I figured the issue would get priority attention by whomever was at fault but I stay up-to-date and the issue persists.
Any insight? Anyone know what I'm talking about? Is there a fix?
Basically, sometimes is stops blinking and the only way to find it is to type something or reset it with your mouse but it remains invisible. Sometimes clicking out of the text field of hovering your mouse pointer over a different text field will trigger it to start blinking but it will usually stop again when you move back to the field you needed it in.
In decades of computing, a functional cursor/insertion point has always been something I could count on. In recent months, it's been F'd up royally. Whoever is responsible should be ashamed. I don't know if a change in graphics drivers (most of the systems I use are nVidia), an updated API/library in Windows, or something with FF4/IE9, but I didn't notice it until several months ago and it has been happening to me on a daily basis ever since (both PCs at home and the PC at work). I didn't say anything at first because I figured the issue would get priority attention by whomever was at fault but I stay up-to-date and the issue persists.
Any insight? Anyone know what I'm talking about? Is there a fix?