Code said:
Whoa Nellie!!!
Zealots, RELAX PLEASE.
The reason I wanted to remove the toolbar and menubar is because this
particular popup is launched from a 3rd party app, so I have no control over
it's original creation state,
Ok. So, you want to control the browser window of your visitors, your
users and if you could, you would want to control the coding of a 3rd
party app, right?
and the one and only purpose of this popup is
for form entry and I simply wanted to increase the odds that the user
wouldn't need to scroll to view the whole form.
Ok, then increase the font size of that form and let's see how people
will scroll that form popup without scrollbars... because this kind of
scenario usually happen often to users over 40.
Why don't you send an email to the web designer of that 3rd party app?
Isn't that the coherent, consequent thing to do in order to address the
real issue?
(All concerns about removing things from the browser should be moot, since
the purpose of this window is not to browse but to enter information into a
form. And if they want to copy the content, gee, the right mouse button lets
them do that, doesn't it? Yes it is your browser, but it's my popup!)
Yeah.. but can they save the page? You know, File/Save as, File/Save
Page as...? can they print the page without the menubar? Remember that
someone in this thread said that some info could be so important that it
would require a popup just to render the info. So, why format the popup
in a way that defeats the pursued purpose of such popup then?
The bottom line is always the same. The more (toolbars, browser
functionalities) you remove from a secondary browser window (via the
window.open() call), the more you make such window useless, unworthy,
unsuitable, anti-user, the more it goes against accessibility to
content. The more (toolbars, browser functionalities) you remove from a
secondary browser window, the more you risk getting your users, your
customers, your visitors run into problems, irritations, difficulties,
fears, whatever. The more (toolbars, browser functionalities) you remove
from a secondary browser window, the more you destroy the user
experience of your site.
The fact that now browser manufacturers are giving back to users
absolute and full veto power over toolbars and browser functionalities
is a sign that your attitude does not promote the users' objective best
interests and the designers' objective best interests in such web
interaction.
After all the firestorm of postings, apparently nobody knows (or is willing
to tell) how to do this!
You never clearly explained the webpage situation; you never talked
about a form, you never talked about scrolling before, you never talked
about a 3rd party app. You only requested technical and very targeted
questions about removing the browser toolbar and menubar in an
non-window.open-ed() browser window and you got a fair, correct and
precise answer on this. In MSIE 6 for windows, it's impossible to remove
the menubar, even if the user wants to remove it, even without an http
connection, without js, even if you were going to pay hundreds of $ to
anyone who would do it.
You're the one who posted very precise and targeted questions and you're
the one who claimed to be able to remove toolbar and menubar in NS which
is simply not true: you need to get full and complete consent from the
user in a confirm popup box to do so... and why in the world would he be
willing to do that? He can View/Show-Hide toolbars as he wishes, as it
pleases without giving a web designer's scripts with unknown intents the
power over his browser window.
BTW, if you plan on coming to my house with rope and gasoline you might as
well bring your crosses and bedsheets too, but I hope your ass is dog bite
and rock salt proof.
DU