Closed
Bug 113772
Opened 24 years ago
Closed 15 years ago
When I use the close-function of Logitech's HyperJump feature, Mozilla closes the whole windows, but it should close only the active tab
Categories
(SeaMonkey :: Tabbed Browser, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: bugzilla-mozilla, Unassigned)
Details
Attachments
(1 file)
5.96 KB,
image/gif
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.6) Gecko/20011120
BuildID: 2001112009
I use a Logitech Cordless Wheel Mouse (but I think this isn't the prob) with the
HyperJump-Feature, that lets me close the active windows just with a click of
the middle mouse button.
When I use tabbing in Mozilla, this function should close only the active tab
and not the whole browser. This is just my opinion, but i often close the window
accidently and have to re-open it...
Reproducible: Always
Steps to Reproduce:
1. Set the Logitech-Mousedriver to use Hyperjump
2. Middle-Click on the Mozilla window
3. Klick on the Hyper-Jump 'X'-button
Actual Results: The whole browser window disappears
Expected Results: If I'm in tabbing mode, I want to close one single tab with
this function
Comment 2•24 years ago
|
||
I need some information on exactly what message the application receives when
this happens.
Comment 3•23 years ago
|
||
I can confirm that the hyperjump function closes the entire window in Mozilla
rather than the tab (20020422 Windows 98).
With applications that keep multiple windows within a single window it
highlights the one you wish to close and only closes that (see screenshot).
Within Painter (the app tested) pressing alt-f4 within any window closed the
entire application.
When using opera and its tabs, although the highlighting is not present but only
the tab you are in is closed (unless you are outside the tab area in which case
the entire window is highlighted).
Another thing to note, is that hyper jump cannot pick up on Moz's scrollbars
(the popup menu functionality was strange in other apps too).
Almost definitely related to other em_exec problems (e.g. bug 20618).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•23 years ago
|
||
Comment 5•23 years ago
|
||
I've no idea what events hyperjump sends - can anyone give me an app that will
tell me?
Comment 6•23 years ago
|
||
This is probably due to the fact HyperJump sends a message
which is processed by MFC widgets and not by those used in
Mozilla (sorry if this is nonsense, I'm not a programmer).
See also bug 160506 for similar behaviour with scroll bars.
Oliver
Comment 7•23 years ago
|
||
I suspect HyperJump sends alt+f4 instead of ctrl+w.
Reporter | ||
Comment 8•23 years ago
|
||
Because Logitech no longer offers the HyperJump feature in MouseWare, I think
this is no longer important. Logitech-support told me that they do not plan to
re-implement HyperJump in future. Therefore I'll hate them but ok, so I don't
use it any more. :-(
And no, it cannot send just Alt+F4 to applications, that would be a very bad
trick. ;-)
Also e.g. Opera takes the command to close its tabs.
Updated•23 years ago
|
QA Contact: sairuh → pmac
Comment 9•21 years ago
|
||
(In reply to comment #8)
> Because Logitech no longer offers the HyperJump feature in MouseWare, I think
> this is no longer important.
Some users (myself included) still use MouseWare 9.4.x merely for HyperJump. It
works perfectly well with WinXP SP2, so there's no good reason to stop using
this amazingly handy feature.
> Logitech-support told me that they do not plan to
> re-implement HyperJump in future.
Last I checked, they told me this:
> Unfortunately the Hyperjump feature is not supported in our later mouseware
> versions. There may be plans to bring it back though with future updates of
> the mouseware software. Please keep checking the Logitech site as new
> driver will be released this month
>
> Kind regards,
> Alan Green
> Logitech Europe SA technical support
Granted, that was a couple of years ago. To the best of my knowledge, nothing
has changed since.
I know the chances that anyone will work on this bug are slim, but I'll be happy
to help, however I can.
I've put a HyperJump-capable version of MW here:
http://oren.gomen.org/Software/Logitech_MouseWare_9.4/
Note that I have very good experience with it with non-Logitech mice, including
Microsoft ones - as long as PS/2 is used. Obviously, YMMV.
Prog.
Updated•19 years ago
|
Assignee: bryner → nobody
QA Contact: pmac → tabbed-browser
Assignee | ||
Updated•17 years ago
|
Product: Core → SeaMonkey
![]() |
||
Comment 10•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
![]() |
||
Comment 11•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•