[FIXED] NoScript bug with Blizzard's battle.net login
Posted: Sat Sep 10, 2011 5:57 am
Hey NoScript Dev(s) and Gurus,
Something with the latest version of Firefox and the latest version of NoScript is preventing authentication with the battle.net login process. I ran into this problem myself, and found some active threads on the World of Warcraft / Battle.net forums. The "enhanced" authentication process pops up a javascript box where users enter username and password. Even with NoScript disabled globally, entering ones information in this box and clicking "Log In" results in the "Processing" message to be displayed indefinitely.
There are two simple workarounds pointed out on the WoW forums. One: disable/uninstall NoScript. It works, but that shouldn't be the route people are going! Two: open the link that normally pops up the java box in a new browser window/tab to access the "low fidelity" login, which does not use javascript. Both workarounds worked for me; I think this is a bug with NoScript.
See the discussion on the WoW forum here: http://us.battle.net/wow/en/forum/topic/2973256088
Discussion on the Starcraft 2 forum here: http://eu.battle.net/sc2/en/forum/topic/2601192828 (Blizzard Tech Support responded, said "disable NoScript," not surprisingly).
Thanks,
wam
Something with the latest version of Firefox and the latest version of NoScript is preventing authentication with the battle.net login process. I ran into this problem myself, and found some active threads on the World of Warcraft / Battle.net forums. The "enhanced" authentication process pops up a javascript box where users enter username and password. Even with NoScript disabled globally, entering ones information in this box and clicking "Log In" results in the "Processing" message to be displayed indefinitely.
There are two simple workarounds pointed out on the WoW forums. One: disable/uninstall NoScript. It works, but that shouldn't be the route people are going! Two: open the link that normally pops up the java box in a new browser window/tab to access the "low fidelity" login, which does not use javascript. Both workarounds worked for me; I think this is a bug with NoScript.
See the discussion on the WoW forum here: http://us.battle.net/wow/en/forum/topic/2973256088
Discussion on the Starcraft 2 forum here: http://eu.battle.net/sc2/en/forum/topic/2601192828 (Blizzard Tech Support responded, said "disable NoScript," not surprisingly).
Thanks,
wam