Can't use keyboard

[Ziggyzoozoo]

I'm playing in high detail in full screen in my window in Firefox 3. However, once in awhile I won't be able to type on my keyboard. I've experienced this on both my Vista laptop and my XP desktop.

 

 

 

 

 

 

 

Has anybody else encountered this and know how to fix this??

[phata_elise]

Perhaps some problems with another firefox add-on?

 

 

 

 

 

 

 

I always play in firefox 3, both on xp and vista and I never had this problem.

[Ziggyzoozoo]

Ahh extensions that's right; both computers have Flashblock installed; that might be the problem. I'll disable whenever I play RS and and see if it still happens.

[Laura]

Do you have the KeyScrambler add-on enabled, by chance?

[hitman76]

I had the same problem, and i couldn't type. but when i closed the internet, restarted the comp it worked... :?

 

 

 

 

 

 

 

then i remember the second time i pressed ctrl or something on the keyboard and it worked again :wall:

 

 

 

 

 

 

 

i remember having the same problem, but sorry i can't remember the remedy :ugeek:

[compfreak847]

That happens when the rune window loses focus from switching to a different window; you have to minimize\maximize the window again and click back on rune before your keyboard will work again.

[Ziggyzoozoo]

Do you have the KeyScrambler add-on enabled, by chance?

 

 

 

 

 

 

 

No, I don't.

 

 

 

 

 

 

 

I had the same problem, and i couldn't type. but when i closed the internet, restarted the comp it worked... :?

 

 

 

 

 

 

 

then i remember the second time i pressed ctrl or something on the keyboard and it worked again :wall:

 

 

 

 

 

 

 

i remember having the same problem, but sorry i can't remember the remedy :ugeek:

 

 

 

 

 

 

 

I thought it might have to do with pressing Control+Shift on my laptop at first, as doing so changes my keyboard settings from "US" to "Canadian French" since I have a multi-lingual laptop, but once I couldn't type on my XP desktop, I knew it had to be something different because I only have one language on my desktop. But yeah to fix it, I just had to open RS in a new window.

 

 

 

 

 

 

 

That happens when the rune window loses focus from switching to a different window; you have to minimize\maximize the window again and click back on rune before your keyboard will work again.

 

 

 

 

 

 

 

That didn't work. I tested this too, I only had RS open, and it suddenly happened; I couldn't use the keyboard despite not having any other windows opened.

 

 

 

 

 

 

 

Anyway, since I have disabled Flashblock, I haven't had this problem, so maybe it was that extension the whole time.

[Laikrob]

Moved to Tech & Computers.

 

 

 

 

 

 

 

Laikrob,

 

 

 

Tip.It Moderator

[compfreak847]

 

Do you have the KeyScrambler add-on enabled, by chance?

 

 

 

 

 

 

 

No, I don't.

 

 

 

 

 

 

 

I had the same problem, and i couldn't type. but when i closed the internet, restarted the comp it worked... :?

 

 

 

 

 

 

 

then i remember the second time i pressed ctrl or something on the keyboard and it worked again :wall:

 

 

 

 

 

 

 

i remember having the same problem, but sorry i can't remember the remedy :ugeek:

 

 

 

 

 

 

 

I thought it might have to do with pressing Control+Shift on my laptop at first, as doing so changes my keyboard settings from "US" to "Canadian French" since I have a multi-lingual laptop, but once I couldn't type on my XP desktop, I knew it had to be something different because I only have one language on my desktop. But yeah to fix it, I just had to open RS in a new window.

 

 

 

 

 

 

 

That happens when the rune window loses focus from switching to a different window; you have to minimize\maximize the window again and click back on rune before your keyboard will work again.

 

 

 

 

 

 

 

That didn't work. I tested this too, I only had RS open, and it suddenly happened; I couldn't use the keyboard despite not having any other windows opened.

 

 

 

 

 

 

 

Anyway, since I have disabled Flashblock, I haven't had this problem, so maybe it was that extension the whole time.

 

 

 

It isn't, I've had flashblock before and it still worked fine. Minimize and maximize the window - it'll work. I have exactly the problem your describing, and it doesn't have to be with multiple windows; simply the java applet losing focus by clicking on the address bar\background\links on the bar above can trigger it, but all are solvable by a minimize\maximize.

[D. V. Devnull]

Ziggyzoozoo, I recommend that you dump FlashBlock forever and go get AdBlock Plus (a.k.a. "ABP") for all of your object-blocking wants and needs. Literally, ABP has all the features you need and more, and you will not have the problems that you are having with FlashBlock now. Also, ABP works better in FF3 than it does in FF2 and earlier... :thumbsup:

 

 

 

 

 

 

 

(BTW, I'm using AdBlock Plus with FF 2.0.0.x-series here. If you need a powerful Advert ~ and other objects ~ Blocking list to start with, mine is continuously in development and evolving well. You could use it as an awesome starting point. Ask me for a copy of my list, if you want it.)

 

 

 

 

 

 

 

~D. V. "Thanks for showing me that FlashBlock stinks." Devnull

[urbestfreind]

*flashblock bashing*

 

 

 

 

 

 

 

I've been using Flashblock along with ABP and NoScript for awhile, and I haven't had a problem. By dumping flashblock, you're dumping a layer of security...It's like saying you don't need a sock because you have a pair of sneakers, and it would just be redundant...It may not seem useful, but that sock does a lot that you don't even consider.

 

 

 

 

 

 

 

Don't dump anything. Find the problem, and fix it. I don't just stop developing a program when the compiler tells me I have an error. I go through, find the error, and fix it, and continue on. Sometimes its a quick find, sometimes it takes me a few hours, but eventually I find it, and everything is good again.

[D. V. Devnull]

 

*flashblock bashing*

I've been using Flashblock along with ABP and NoScript for awhile, and I haven't had a problem. By dumping flashblock, you're dumping a layer of security...It's like saying you don't need a sock because you have a pair of sneakers, and it would just be redundant...It may not seem useful, but that sock does a lot that you don't even consider.

 

 

 

 

 

 

 

Don't dump anything. Find the problem, and fix it. I don't just stop developing a program when the compiler tells me I have an error. I go through, find the error, and fix it, and continue on. Sometimes its a quick find, sometimes it takes me a few hours, but eventually I find it, and everything is good again.

And you apparently didn't notice that FlashBlock was the problem, causing Ziggyzoozoo extreme trouble with RuneScape... Worse, it happened to be to such point that they were unable to use a most basic tool (their keyboard, and therefore their normal text chat) with the game applet in fullscreen mode. On top of that, it was a situation set up for failure, because some OpenGL-enabled setups develop problems with any weird layouts that a user wishes to use. (I have actually been forced to shut down whole secondary monitors to play some full screen games here at home, simply because the OpenGL subsystem that FireFox calls ~ or something that another app calls to go fullscreen ~ will not handle the secondary monitor for those items! So do not act like I'm talking [bleep] and being an idiot, because I'm not!)

 

 

 

 

 

 

 

~Mr. D. V. "I've actually seen weird things result from OpenGL (and Direct3D) with a setup that isn't compatible." Devnull

[prostar]

is the keyboard connected via usb?

 

ive have had keyboard problems recently too when playing full screen high detail, and its as if all of a sudden the keyboard isnt recognised as connect and has a massive spasm often spinning the rs game view in a circle..?

 

any ideas to what the problem is?

[dsavi]

^ The keyboard problems are fixed, when you click off RS it loses focus -> RS doesn't work unless you click on it again.

 

 

 

This has absolutely nothing to do with flashblock. RS runs on Java.

[D. V. Devnull]

(While I hate to further discuss a solved item that's 10 days old, this has to be answered...)

 

 

 

This has absolutely nothing to do with flashblock. RS runs on Java.

Wrong again. :roll:

 

 

 

Both the FlashBlock extension and Java have to deal with the browser and the navigation system within, as well as the javascripting systems that both extensions and plugins rely upon to do what they do... Further, FlashBlock was stealing it an inopportune times, causing Ziggyzoozoo to have problems until they disabled FlashBlock. Now while the browsing elements work excellently under Internet Explorer (of course by MicroSoft's design) and focus will return to the applet, it doesn't work so well under Mozilla FireFox because the developers didn't have the foresight to throw the focus back to the applet even if an item in an IFrame tag was loading. And so with how FlashBlock is designed, it was glitching up the keyboard focus and sending everything to hell. :geek:

 

 

 

This is why I have recommended AdBlock Plus to replace FlashBlock... In fact, I should have attached to my last post a copy of the filterlisting needed to flat strip most (The user will still need to develop "second pass"-type filters for what remains, without breaking Jagex's final advert scripts.) of what could happen from having to readapt due to this problem. :| ... Here it is, with recommendation that the user manual be read and/or help requested further in here, before putting them in (unless the user grips onto what to do easily)...

 

 

 

[hide=ABP Filter Listing, Click to view...]advert.runescape.com*banner.ws?size=301

 

advert.runescape.com*banner.ws?size=728

 

advert.runescape.com*banner.ws?size=729

 

advert.runescape.com*banner.ws?size=730

 

advert.runescape.com*banner.ws?size=734

 

advert.runescape.com*banner.ws?size=735

 

advert.runescape.com*banner.ws?size=738

 

runescape.com#div(class*=adframe)

 

runescape.com#span(id*=vbUrl)

 

runescape.com#div(id*=tb)

 

advert.funorb.com

 

funorb.com#iframe(id*=ad)[/hide] FlashBlock will have to be bugfixed by its' author before it will quit having the behavior that Ziggyzoozoo experienced. :(

 

 

 

~D. V. "I know a cross-linked problem when I see one." Devnull

[dsavi]

(While I hate to further discuss a solved item that's 10 days old, this has to be answered...)

 

 

 

This has absolutely nothing to do with flashblock. RS runs on Java.

Wrong again. :roll:

 

 

 

Both the FlashBlock extension and Java have to deal with the browser and the navigation system within, as well as the javascripting systems that both extensions and plugins rely upon to do what they do... Further, FlashBlock was stealing it an inopportune times, causing Ziggyzoozoo to have problems until they disabled FlashBlock. Now while the browsing elements work excellently under Internet Explorer (of course by MicroSoft's design) and focus will return to the applet, it doesn't work so well under Mozilla FireFox because the developers didn't have the foresight to throw the focus back to the applet even if an item in an IFrame tag was loading. And so with how FlashBlock is designed, it was glitching up the keyboard focus and sending everything to hell. :geek:

 

 

While that all makes sense, I'm not too sure where you got that from.

[D. V. Devnull]

(While I hate to further discuss a solved item that's 10 days old, this has to be answered...)

 

 

 

This has absolutely nothing to do with flashblock. RS runs on Java.

Wrong again. :roll:

 

 

 

Both the FlashBlock extension and Java have to deal with the browser and the navigation system within, as well as the javascripting systems that both extensions and plugins rely upon to do what they do... Further, FlashBlock was stealing it an inopportune times, causing Ziggyzoozoo to have problems until they disabled FlashBlock. Now while the browsing elements work excellently under Internet Explorer (of course by MicroSoft's design) and focus will return to the applet, it doesn't work so well under Mozilla FireFox because the developers didn't have the foresight to throw the focus back to the applet even if an item in an IFrame tag was loading. And so with how FlashBlock is designed, it was glitching up the keyboard focus and sending everything to hell. :geek:

 

While that all makes sense, I'm not too sure where you got that from.

The logic is compiled from several sources. :geek:

 

 

 

First, my knowledge of what happened to me while using FireFox without any advert blocking (Which resulted in my losing control of the RuneScape applet every time an advert loaded.)... Second, what was happening to Ziggyzoozoo (They lost focus ONLY while FlashBlock was enabled, it stopped when they stopped using FlashBlock.)... Finally, there was the small pack of knowledge I picked up on the way while studying about how FireFox was designed and works (Mozilla's pages on working with the 'about:config' system gave some nifty pointers too, inclusive of the fact that a feature called "spatial navigation" wasn't put into the default FireFox builds, which would have possibly handled this issue.) ... :-k

 

 

 

When I looked at it, it was like a light clicked on in my head. Everything that was happening fit the problem that Ziggyzoozoo had run into. For that matter, it has now also dawned on me that these extensions, even when they aren't actively in use, have some kind of basic item within that listens for something (which could range anywhere from a keyboard/menu shortcut to a keg of incoming page data) that they're supposed to be handling. Which would add to explaining what happened with the FlashBlock add-on, because having such a listener that is not designed properly could result in some of the same kinds of focus-stealing issues... :?

 

 

 

I hope this additional info helps your understanding of my earlier post. :)

 

 

 

~D. V. "The logic connects..." Devnull