Detecting onmouseup outside browser window?

[Mandy Memphis]

If I perform a mousedown within a document, move the mouse outside the
browser window, and then release the mouse button, the document.onmous eup
event does not fire. Is there any way to detect a mouseup event outside the
document?

Also, how can I get the relative coordinates of the cursor while it is
outside the browser?

Thank you.

[Randy Webb]

Mandy Memphis wrote:

<--snip-->

When I see code like this:

href="javascr ipt:void(0)"

I tend to stop reading anymore, as the author code such as that isn't
very aware of reality on the web.

He was aware enough to get something to work that you said couldn't be done!
;-P

No, because it doesn't work.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq/

[Randy Webb]

Matt Kruse wrote:

Randy Webb wrote:

When I see code like this:
href="javascr ipt:void(0)"
I tend to stop reading anymore, as the author code such as that isn't
very aware of reality on the web.

I don't think that's a fair statement.
Obviously, Mr. Zorn is not a newbie script kiddie, and to be so judgemental
of his abilities based on a snippet of code is a bit unwarranted, IMO.

No, he is not a newbie script kiddie, but I still tend to discount code
written that has snippets of that in it. I also tend to discount code
that has attempted obfuscation in it, and thats based on his .js file.
--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq/

[Mandy Memphis]

"Randy Webb" <hi************ @aol.com> wrote in message
news:7o******** ************@co mcast.com...

Mandy Memphis wrote:

<--snip-->

When I see code like this:

href="javascr ipt:void(0)"

I tend to stop reading anymore, as the author code such as that isn't
very aware of reality on the web.

He was aware enough to get something to work that you said couldn't be done! ;-P

No, because it doesn't work.

Work for me.

[Andrew Thompson]

On Tue, 6 Jul 2004 21:40:04 -0400, Mandy Memphis wrote:

No, because it doesn't work.

Work for me.

The natural assumption on this group is that you
are developing for the web unless otherwise stated.

On the web, it does not work. ( Note that you
have already had a 50% failure rate in the
4 tests conducted. )

--
Andrew Thompson
http://www.PhySci.org/ Open-source software suite
http://www.PhySci.org/codes/ Web & IT Help
http://www.1point1C.org/ Science & Technology

[Matt Kruse]

Andrew Thompson wrote:

The natural assumption on this group is that you
are developing for the web unless otherwise stated.
On the web, it does not work. ( Note that you
have already had a 50% failure rate in the
4 tests conducted. )

It would be more correct to say that on the web, it does not work with all
browsers, but most likely does work for the majority of users. Also, it
appears to degrade gracefully (not causing any problems in browsers where it
doesn't work) which is exactly what we'd want.

So, in summary, it appears to be a fantastic solution, IMO.

--
Matt Kruse
Javascript Toolbox: http://www.JavascriptToolbox.com/

[Andrew Thompson]

On Wed, 7 Jul 2004 11:14:37 -0500, Matt Kruse wrote:

..50% failure rate in the
4 tests conducted.

It would be more correct to say that on the web, it does not work with all
browsers, but most likely does work for the majority of users. Also, it
appears to degrade gracefully (not causing any problems in browsers where it
doesn't work) which is exactly what we'd want.

Doesn't have the same ring to it as..
"50% failure rate in the 4 tests conducted."
...which is an accurate statement.

--
Andrew Thompson
http://www.PhySci.org/ Open-source software suite
http://www.PhySci.org/codes/ Web & IT Help
http://www.1point1C.org/ Science & Technology

[Matt Kruse]

Andrew Thompson wrote:

Doesn't have the same ring to it as..
"50% failure rate in the 4 tests conducted."
..which is an accurate statement.

a) Flawed statistics are meaningless. "100% success rate in the browsers
used by 94% of site visitors" is another statistic which might be accurate.
b) Every single javascript every written will fail in at least one situation
c) It doesn't really matter, since the solution does exist, works nicely in
a subset of browsers, and degrades gracefully - everything js code should
do. :)

--
Matt Kruse
Javascript Toolbox: http://www.JavascriptToolbox.com/

[Richard Cornford]

Matt Kruse wrote:

Andrew Thompson wrote:

The natural assumption on this group is that you
are developing for the web unless otherwise stated.
On the web, it does not work. ( Note that you
have already had a 50% failure rate in the
4 tests conducted. )
It would be more correct to say that on the web, it does not work
with all browsers,

Surly it does not work with all browser whether on the web or not. The
web is just the place where it can expect to encounter all browsers (or
at least stand a chance of encountering them).
but most likely does work for the majority of
users. Also, it appears to degrade gracefully (not causing any
problems in browsers where it doesn't work) which is exactly what
we'd want.
Well, we have a thread about monitoring the mouseup event outside of the
window/document, and that definitely does not work on many browsers, and
then only under some circumstances (only when dragging in IE, for
example).

The code under discussion does make a reasonable attempt at clean
degradation, but it is a long way from being cross-browser, reliable or
good. And some of the implementation details make me think that it could
be extremely problematic on Safari or Konqueror (to name but two) with
the script partly running and then erroring mid process due to the use
of object-inference browser detection instead of the feature detection
that it almost achieves. That type of uncontrolled failure mid flow is
likely to undo the good work put into clean degradation by leaving the
page in an intermediate state that may not be nearly as viable as the
original HTML.
So, in summary, it appears to be a fantastic solution, IMO.

If you understood what the script was doing you would not be attaching
"fantastic" to it as a label. It is an above average script with some
serious design flaws and as a result should only be expected to exhibit
planned behaviour on the limited test-set of browsers stated in its
documentation.

It is actually a bit disappointing as a product of its author as his
vector graphics library is a really good implementation of efficient
line and arc drawing algorithms in javascript. Which contrasts horribly
with a script that even features an eval-ed dot notation property
accessor.

Richard.

[John Smith]

"Randy Webb" <hi************ @aol.com> wrote in message
news:7o******** ************@co mcast.com...

Matt Kruse wrote:

Randy Webb wrote:

When I see code like this:
href="javascr ipt:void(0)"
I tend to stop reading anymore, as the author code such as that isn't
very aware of reality on the web.

I don't think that's a fair statement.
Obviously, Mr. Zorn is not a newbie script kiddie, and to be so judgemental of his abilities based on a snippet of code is a bit unwarranted, IMO.

No, he is not a newbie script kiddie, but I still tend to discount code
written that has snippets of that in it. I also tend to discount code
that has attempted obfuscation in it, and thats based on his .js file.

I'm not sure if he has deliberately obfuscated it, but it isn't very clear,
that's for sure. His attitude seems to be "why do something in 10 lines when
you can do it all in one", and "why name something intuitively when you can
use two random letters". Maybe it's because he's German? :) However, it
seems to work well in IE anyway. As for Mandy's problem...

In IE you can capture the document.onmous eover event and return false from
it in order to cancel the default action (which is to stop updatng the mouse
coords beyond the window boundary). The mouse coords can then be read from
the event.clientX and event.clientY properties. Another side effect of doing
this is that the document.onmous eup event will now fire while the mouse is
outside the browser (while the browser is active). Note that setting the
event.cancelBub ble property in the document.onmous eover event is independent
of cancelling the default action.

HTH

[Grant Wagner]

Matt Kruse wrote:

Andrew Thompson wrote:

Doesn't have the same ring to it as..
"50% failure rate in the 4 tests conducted."
..which is an accurate statement.
a) Flawed statistics are meaningless. "100% success rate in the browsers
used by 94% of site visitors" is another statistic which might be accurate.

His statistics aren't flawed. His choice of tests or his testing methodology
might be, causing him to get the failure rate he desires, but the statistics
themselves are (presumably) accurate. Of the four tests he chose to conduct, the
page failed half the time. The trick lies in finding the right four tests to
use.
b) Every single javascript every written will fail in at least one situation
This depends on how you define "failure". If the code never executes, then can
it be considered to have "failed".

I doubt <script type="text/javascript">var n = 0;</script> has ever failed in at
least one situation, unless you define failure to include not executing at all
(in the case of a user agent which does not support JavaScript, or JavaScript is
not enabled).
c) It doesn't really matter, since the solution does exist, works nicely in
a subset of browsers, and degrades gracefully - everything js code should
do. :)

I right-clicked the links in question and chose "Open Link in New Active Tab". I
got a blank document. Not too graceful a degradation.

I'm not particularly sure what would be so terribly wrong with:

<a href="noJS.html " onclick="...;re turn false;">...</a>

with noJS.html:

<html>
<head>
<title>JavaScri pt not enabled or link not single clicked</title>
</head>
<body>
<p>You need JavaScript enabled to enjoy what this link does. Be sure to single
click the link with your primary mouse button to activate it.</p>
</body>
</html>

Simple to implement, does not require much more work then <a
href="javascrip t:void(0);" ...> and would avoid silly arguments on usenet.

--
Grant Wagner <gw*****@agrico reunited.com>
comp.lang.javas cript FAQ - http://jibbering.com/faq