ASM wrote :
because return false;
return false cancels the default action of the element, here it cancels
the default action of the link. In case javascript is disabled, then the
link should open the photopage#.htm?region=#slave.region# resource in a
named window called "prop1". This is important if you want to maximize
the resources your code uses from the users' system resources.
Re-opening and re-using/re-cycling an already opened secondary window is
the most efficient way to use the user's system resources.
"The purpose of the return false in the code is to cancel default action
of the link: if the onclick event handler is executed, then there is no
need to execute the default action of the link. But if javascript
support is disabled or non-existent on the user's browser, then the
onclick event handler is ignored and the browser loads the referenced
resource in the target frame or window (...)"
http://developer.mozilla.org/en/docs/DOM:window.open#Best_practices
Wasn't it what wanted ?
Which reasons ?
I think I've seen at mozilla.org(*)
that height and width would have to be dimensions of viewing area
No. Read again. When the web developer codes the window.open() call and
the height and width windowFeature, he's requesting some particular
value for the height and width of the browser window viewport of that
new window to be.
Everything is nicely explained at
http://developer.mozilla.org/en/docs/DOM:window.open#height
So, f you know which space you need,
why not to freeze a naked window to this size ?
Without knowing it, you are exactly making my point regarding always
ensuring that a window is resizable and renders scrollbar(s) if content
exceeds, overflows requested window dimensions. In this case, if the web
developer goes wrong with the requested width and/or height, then a
normal, standard fallback mechanism should prevail and should let the
user adjust the size of that new window according to his needs. Failure
to do so makes the window inaccessible, difficult to use, frustrating to
the user.
Often, the user gets a new window without knowing it in advance; and
often, he gets a crippled window. The result is easy to figure out: the
user closes the stupid window and leaves the web developer's site
without him never knowing about his bad work.
Gérard