My OperaYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
Bug in 10.53? Disabled state of Quick Preference "Enable JavaScript" ignored.............?
Bug in 10.53:Disabled state of Quick Preferences "Enable JavaScript" ignored if appropriate option "Enable Javascript" in Site Preferences is Enabled?
In <=10.52 if I disable JavaScript using Quick Preferences "Enable JavaScript", javascript become disabled ignoring appropriate option in "Site Preferences". And that was good. Now I forced to go to Site Preferences and disable/enable JavaScript there(and I can do that only there) and additionally reload page. It is heavily irritating, especially during debugging web-pages(Ability quickly disable JavaScript is very useful when debugging web-interfaces which must identically work in both case of Enabled/Disable JavaScript, no other browser have such ability).
Please revert old behavior.
30. April 2010, 17:20:28 (edited)
I tested this on this forum page:
If this behaviour has changed in Opera 10.53 then it seems to have changed in the right way.
If no change has ever been made in site preferences to the javascript options, the global setting should take effect.
However, if a change has been made in site preferences, the global setting should be ignored for that site.
Is this not what you would expect?
To reset site preferences to no changes go to Preferences, Content, Manage site preferences, and delete the entry for the site you want to reset.
- Initial State: Javascript was enabled and in site preferences as expected
- I disabled javascript in quick preferences and it was then disabled in site preferences as expected
- I enabled javascript again in quick preferences and it was then enabled in site preferences. So far, so good.
- I disabled javascript in quick preferences and it was then disabled in site preferences
- I enabled javascript in site preferences
- I enabled javascript in quick preferences and it was still enabled in site preferences as expected
- I disabled javascript in quick preferences and it was then still enabled in site preferences, as expected
If this behaviour has changed in Opera 10.53 then it seems to have changed in the right way.
If no change has ever been made in site preferences to the javascript options, the global setting should take effect.
However, if a change has been made in site preferences, the global setting should be ignored for that site.
Is this not what you would expect?
To reset site preferences to no changes go to Preferences, Content, Manage site preferences, and delete the entry for the site you want to reset.
Skins Tips Buttons Backup Security User Scripts Language Forums
Browser JS Changelogs Opera Next Dragonfly Bugs FTP
My Website Opera Review My Fonts IrfanView Search Downloads
Opera 11.64 on Windows 7 64-bit • AMD A10-6800K, 8 Gbyte RAM specs
Rules of Conduct and Posting Rules • Please Don't Shout • Editing Posts • Opera Config Links
Browser JS Changelogs Opera Next Dragonfly Bugs FTP
My Website Opera Review My Fonts IrfanView Search Downloads
Opera 11.64 on Windows 7 64-bit • AMD A10-6800K, 8 Gbyte RAM specs
Rules of Conduct and Posting Rules • Please Don't Shout • Editing Posts • Opera Config Links
> If no change has ever been made in site preferences to the javascript options, the global setting should take effect.
Agreed. It works.
> However, if a change has been made in site preferences, the global setting should be ignored for that site.
Agreed. In 10.52 it wasn't so. In 10.53 I do not checked it.
> Is this not what you would expect?
Not, it is not.
Read carefully: "QUICK preferences" synonym "Operative preferences" They intended to be used when user need quickly change them. And so they MUST indicate current state of option in current situation(Neither global setting, nor site setting, but operative setting for current tab(not site!)(i.e. when tab is closed - Quick setting must be forgotten, and never should be saved in persistent storage like global setting or site settings)), and must be took into account by browser as quickly as possible independently of other settings. Else then cannot be called QUICK preferences. In 10.53 Quick Preference "Enable JavaScript" does not indicates real state of JS Engine when Site-preference was alerted. You can trigger as many time as you want, effect will multiplied by zero. So they are not QUICK preferences more. They are unusable now. That is wrong.
SO I can conclude bug:
Quick Settings "Enable JavaScript", "Enable Animated Images", "Enable Sound in Web Pages", "Enable Plug-Ins", "Send Referrer Information" etc
must be disabled(grayed menu items) if corespondent setting in "Site Preferences" was alerted since they does not effect anything.
> To reset site preferences....
Agreed. It works.
> However, if a change has been made in site preferences, the global setting should be ignored for that site.
Agreed. In 10.52 it wasn't so. In 10.53 I do not checked it.
> Is this not what you would expect?
Not, it is not.
Read carefully: "QUICK preferences" synonym "Operative preferences" They intended to be used when user need quickly change them. And so they MUST indicate current state of option in current situation(Neither global setting, nor site setting, but operative setting for current tab(not site!)(i.e. when tab is closed - Quick setting must be forgotten, and never should be saved in persistent storage like global setting or site settings)), and must be took into account by browser as quickly as possible independently of other settings. Else then cannot be called QUICK preferences. In 10.53 Quick Preference "Enable JavaScript" does not indicates real state of JS Engine when Site-preference was alerted. You can trigger as many time as you want, effect will multiplied by zero. So they are not QUICK preferences more. They are unusable now. That is wrong.
SO I can conclude bug:
Quick Settings "Enable JavaScript", "Enable Animated Images", "Enable Sound in Web Pages", "Enable Plug-Ins", "Send Referrer Information" etc
must be disabled(grayed menu items) if corespondent setting in "Site Preferences" was alerted since they does not effect anything.
> To reset site preferences....