Dominic Tocci wrote :
My dilemma is caused by tabbed browsing and "tabbrowser preferences". I
have a chromeless window, from which I want to spawn fully functional pop-up
windows. Basically, I want to replicate the same behavior as
<a href="
http://www.yahoo.com" target="_blank">click here</a>
but I always want the page in a new window, not a new tab.
You can not force that. Already K-meleon 0.9, Mozilla 1.8b2, Firefox
Deer Park alpha 1 give (possibly) 100% control over these issues to the
users.
When something
opens in a new tab in a window without any chrome it becomes unaccessible.
Tabbrowser preferences forces the html code above to open in a new tab.
That's one reason among many others why coding of links should be
careful: nothing (at least regarding requested popups and use of
window.open) can be forced anymore and one has to evaluate accessiblity
of links. This trend won't change. You can expect MSIE 7 to implement
tab-browsing (that is already not a rumor but a solid fact).
The
only way I have found to override the tab functionality is by window.open
and the code I included.
Nope. Not true. Mozilla 1.8b2, Firefox Deer Park alpha 1 already offers
users ways to go around (almost) any window.open calls. Same thing with
k-meleon 0.9 and possibly other tab-capable browsers.
I can force all parts of the chrome to appear
except for the illusive "extraChrome" stuff, which apparently includes the
sidebar. (The code works in IE, but not in firefox.)
For some reason, your proposed solution does not override the common plugin
"tabbrowser preferences" at all.
No and my proposed solution should not override or overcome the user
settings, prefs, advanced features. My proposed solution should
sidestep/move out of the way of the users' prefs, advanced settings, etc..
On my own website, I do not try to work against the users' freedom,
preferences or try to work despite/regardless of the users' prefs,
advanced settings; I try to work in accordance to his freedome,
preferences, advanced settings. So every link that opens a new window is
clearly, explicitly identified so that the user can override such
opening mode and have/impose his own preferred mode of opening link
whatever it might be:
- in a new secondary window
- in a new tab in the same window
- in the same tab of the same window
- in the background
- not in the background (with focus transferred)
In your example, the new window simply
opens in a new tab for me, so I'm back to it being inaccessible.
It's the other way actually. If you were to create a new window by
force, your code would be considered as anti-accessible because it
removes flexibility from the user, it would go against the will of
users, against their prefs, their settings.
Gérard