127339 - Cleaner implementation of Scripts and Windows Preferences

Status: RESOLVED EXPIRED

(SeaMonkey :: Preferences, defect)

Description

[Rafael Ebron (:rebron)]

Proposing a cleaner implementation for the Scripts and Windows preference.  We
should use the same implementation that hewitt did for location bar auto complete.

In the advanced panel
[]Enable Java
[]Enable Javascript for Navigator (MORE) button
[]Enable Javascript for Mail & Newsgroups

1)  The more button will open up a window 
Allow script to:
Open unrequested windows
etc.

2)  If enable javascript for navigator is turned off, the more button should be
disabled.

Comment 1

[Warner Young]

No offence, but although this would be more consistent with the Smart Browsing
panel, I think it's bad UI design.  All it does is add an additional layer of
interaction for the user.  IMHO, the fewer clicks that are needed, the better. 
I suspect the only reason location bar autocomplete was put in its own dialog
with a More button is that there isn't enough room in the Smart Browsing panel
to accommodate the feature.

Comment 2

[Rafael Ebron (:rebron)]

What I'm seeing and hoping to prevent is a preference list that is ever
expanding and getting larger every release.

There are 7 folder items.
With Appearance there are 5 screens of prefs, 
7 screens for Navigator 
2 for composer
6 for Mail & Newsgroups
9! for Privacy and Security
and 7 for the Advanced panel
1 for Offline

And, we're not even counting add-ons such as Annozilla, Blogbar and many other
components.  

My 2 cents.  

Should go over to UE and get a spec, mpt or marlon to take a look for post 1.0.
 Not pushing as a nsbeta1 bug.

Comment 3

[Samir Gehani]

-> Marlon

Comment 4

[André Dahlqvist]

Dupe of bug 115353?

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420