128925 - browser.target_new_blocked renamed - update customizing.html

Status: VERIFIED FIXED

(Documentation Graveyard :: Help Viewer, defect)

Description

[Jeremy M. Dolan]

I have browser.target_new_blocked turned on in prefs.js, and also 'new windows
open in new tabs' in tab browser prefs. Clicking 

Shane at 98lite.net

on the URL loads a new window. I disabled the tab browsing pref and still it
loads in a new window. Did someone bust this pref? Severe severe perf problems
for my poor 266mhz p2 if new window isn't disabled.

Comment 1

[Matthias Versen [:Matti]]

which Build ID ?

-> Dupe of bug 126224 ?

Comment 2

[Jeremy M. Dolan]

not a dupe, and todays branch.

Comment 3

[Jonas Jørgensen]

browser.target_new_blocked has been renamed to browser.block.target_new_window
and is now accessible through Preferences|Advanced|Scripts & Windows. This
happened with the checkin for bug 78037. I meant to mention this in the
newsgroups but I forgot. Sorry. I did contact the maintainers of
<http://geocities.com/pratiksolanki/> and
<http://mozilla.org/unix/customizing.html>, though.

Although this bug is invalid, I think we should leave it open for a couple of
weeks or so so that it will show up in queries in case someone else thinks of
filing it, so I'm reassigning it to me to make it disappear from mstoltz's list.

Comment 4

[Jeremy M. Dolan]

OK, a few things.

Would it be an idea to have an alert on startup if there's an invalid pref in
prefs.js, so there's some indication that something's changed? Most apps do this.

The new wording in scripts&windows for the two new window prefs is AWFUL. I even
understand target= and window.open, and I haven't the SLIGHTEST clue what those
two may or may not affect.

I'll consider this bug fixed if http://mozilla.org/unix/customizing.html is
updated (preferably with a note that it was changed, so it's more noticable).

Comment 5

[Jonas Jørgensen]

> The new wording in scripts&windows for the two new window prefs is AWFUL. I
> even understand target= and window.open, and I haven't the SLIGHTEST clue
> what those two may or may not affect.

I agree with you, but it's Jatin who decides those things, if I understand
correctly, and it's his wording that I used in the patch.

> I'll consider this bug fixed if http://mozilla.org/unix/customizing.html is
> updated (preferably with a note that it was changed, so it's more noticable).

Very well, updating summary and assigning to the maintainer of
<http://mozilla.org/unix/customizing.html>.

Comment 6

[Akkana Peck]

The customizing document has been updated.

Comment 7

[Jonas Jørgensen]

Yup.