284143 - Javascript option "But disable common annoyances" sets options on disable, not on enable

Status: RESOLVED WORKSFORME

(Firefox :: Settings UI, defect)

Description

[Ger Teunis]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050228 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050228 Firefox/1.0+

When disabling Javascipt option "But disable common annoyances" the
"dom.disable_window_open_feature.status" and "dom.disable_window_status_change"
are set to TRUE.
When enabling "But disable common annoyances" it does NOT set the 2 options to
false again.
A error in disabeling/enabling "But disable common annoyances"?

Reproducible: Always

Steps to Reproduce:
1. Open about:config
2. Set "dom.disable_window_open_feature.status" and
"dom.disable_window_status_change" to FALSE
3. Go to options, content and enable "But disable common annoyances" (the step 2
options do not change).
4. Disable "But disable common annoyances", the step 2 options are set to TRUE.
5. Enable "But disable common annoyances" again, step 2 options are still TRUE.




The 2 options are clearly set to TRUE when the "But disable common annoyances"
is disabled.
The options are not set to FALSE when the "But disable common annoyances" is set
to true.

Comment 1

[Dave Townsend [:mossop]]

WFM

I see both prefs TRUE when disable annoyances is enabled and FALSE when disabled
and they happily change between as I would expect.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050228
Firefox/1.0+

Comment 2

[Ger Teunis]

I figured it out:
It is only triggered when the about:config is opened during "But disable common
annoyances" change. I figure this might be another bug resulting in options not
correctly changed when about:config is opened.

Comment 3

[Dave Townsend [:mossop]]

I did my testing with about:config open.

Comment 4

[Ger Teunis]

Call me crazy: it can't reproduce it anymore. I did really test it over and over
(all possible testcases). Weird. I resolve it to INVALID myself.

Comment 5

[Ger Teunis]

Sorry for the bugspam, should be WORKSFORME.

Comment 6

[Dave Townsend [:mossop]]

I am concerned that there is something going on here. I experienced a similar
situation, testing some preferences from the options pane and finding them not
working at all, then all of a sudden they started working again. Hopefully there
isn't some intermittent problem here.

Comment 7

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change