Closed Bug 582227 Opened 14 years ago Closed 14 years ago

"Enable Java script" Feature does not apply saved settings until browser restart

Categories

(Firefox for Android Graveyard :: General, defect)

x86
Android
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: vladmaniac, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3pre) Gecko/20100726 Minefield/4.0b3pre
Build Identifier: 20100727 [android]

The "enable JavaScript" button in Content Menu has two states: YES and NO. Tapping one of them will change current setting with the opposite one. 
After navigating a javascript test page such as http://www.randomibis.com/coolclock/ it retains state of behavior even if javascript settings are changed.
Settings are submitted only after browser restart. 

Reproducible: Always

Steps to Reproduce:
1.Open Fennec
2.Slide screen from right to left to open the Options Menu
3.Select Preferences by tapping Preferences icon
4.Slide down if necessary until Content section is visible
5.Inspect Enable JavaScript Menu Item. Tap on right YES/NO button to change state
6.Go back and navigate http://www.randomibis.com/coolclock/
Actual Results:  
Notice the test page behavior is not changing according to new javascript settings. Settings are saved only after killing Fennec and restarting. 

Expected Results:  
If java script is disabled after changing button state, you should not see any clocks on screen. And viceversa.  

Note:
If trying to reproduce this, I suggest using this link also for a javascript test:

http://hg.mozilla.org/qa/litmus-data/raw-file/tip/firefox/popups/coolclock/demo.html
OS: Other → Android
What if you just refresh the page? Don't close Fennec, just press the "refresh
button (or F5 on desktop)
You can refresh the page but with no results. It's not expected for Fennec to update the page according to new settings without performing refresh.
Status: UNCONFIRMED → NEW
Ever confirmed: true
It seems that problem is not regressive for the new maemo5 build on date 20100801.Therefore, I put status to RESOLVE/WORKSFORME
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.