Steve said:
DU wrote in message ...
Look - If the *solution* to his puzzle ... whatever, is just one word or a
graphic, then a small pop-up window with the *solution* will be more than
adequate.
As coded, *your code* will not work for 8% to 12% of all users out there
who have javascript support disabled. No word in a popup. No graphic in
a popup. Nothing. Zero. Nil.
There is such a thing as abusing user's system resources, you see. Popup
coding involves creating, building window frames, borders, toolbars,
size, positioning, security, memory management, storing and retrieving
persistent data, etc and popup code in browser executable involves lots
of instruction code, just in case you ignore this. So, if you're going
to suggest and support the popup approach, at the very least provide one
that meets usability standards, accessibility guidelines and respect as
much as possible user's system resources.
If the solution to his puzzle is just 1 word or a graphic, then a popup
is less justified and less justifiable as a solution.
He's able to size the pop-up to fit his answer.
As coded, *your code* will annoy the user if the user needs to resized
the popup, and this, for whatever reasons he would need/want to resize
such popup. Often web designers do not consider browser default margins
on the body element.
If you believe the popup is correctly sized, then why do you fear making
it resizable? What's the safe, cautious, flexible approach (from the
user's perspective) to sizing a popup? To make it rigid and unresizable
or to make it resizable?
Why people are requested help on this then?
"Unable to Maximize or Resize Internet Explorer Pop-Up Windows"
http://support.microsoft.com/default.aspx?scid=kb;en-us;211068
The user is able to move
the pop-up around to compare the answer with the user's own efforts ...
easy.
Why do others have to make things so complicated when a simple answer
serves?
This is what you wrote in the "Open in new window ??......." thread just
yesterday:
"if you suspect the link doesn't open in a new window
and you try the right-click option it still doesn't work if it's a
javascript link, so when you realise you just close it and do a *normal*
left-click."
Now, for someone speaking of simple answer, simple solution that works,
you certainly have your javascript understanding, explaining pretty
twisted. You're entirely contradicting yourself: your code and your
explanations are incoherent, inconsequent. You're coding a solution that
you know creates problems!
http://jibbering.com/faq/#FAQ4_24
"When they want the destination to appear in a new page, they can use
their browser's 'open in new window' command -- assuming, of course,
that **the link is not a piece of code that interferes with the
browser’s standard behavior.**"
Top Ten Web-Design Mistakes of 2002
6. JavaScript in Links
http://www.useit.com/alertbox/20021223.html
and that is exactly what the code you provided in this thread do.
" * Don't use javascript: URLs
Using a straight http: URL will allow any browser to access the
link. If you want to use JavaScript for browsers that have JavaScript
enabled, use the onMouseOver and onClick attributes of the <a href> tag.
(...)
* wrong:
<a href="javascript:window.open(blah)">
* right:
<a href="foo.html" target="_blank" onClick="window.open(blah);
return false">
"
http://www.panix.com/~aahz/javascript.html#remove
The OP hopefully knows what he's doing.
Anyone could copy and paste a DreamWeaver function code, you know,
without understanding its flaws, limitations, usability burden, without
justification for its implementation.
Even if he doesn't, at least when
we see the final result we can critic.
You provided a complete webpage code, from <html> to </html> in this
thread. And it had flaws and weaknesses that anyone could see and can
verify all by himself.
DU