Closed
Bug 308503
Opened 19 years ago
Closed 19 years ago
middle mouse clicks partly broken
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: spam, Assigned: csthomas)
References
Details
(Keywords: regression)
20050913 SeaMonkey/1.1a
when clicking with the middle button (scrollwheel click) i get a square "scroll
icon" when i try to middle-mouse paste in forms or scroll on slidebar.
This has happened the last week and I consider it a major annoyance and
usability setback
My prefs are:
greprefs/all.js:
pref("middlemouse.scrollbarPosition", true);
prefs.js:
user_pref("middlemouse.paste", true);BZ: Using WinXP and seeing this regression with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050913 SeaMonkey/1.1a (Build ID 2005091306)
sorry.. broke between 9th and 10th this month broke in 2005091005
oops.. i'm wrong. Hold it, i'll find the correct regression window
OK - I've triple checked, full installs/uninstalls: Trunk Semonkey 2006090406 is the last OK build. There's a gap in builds - none for the 5th and 6th. The next one, 2005090705, is where this is broken. Full installs from seamonkey-1.1a.en-US.win32.installer.exe
There's another bug in 2004090406 which is GONE in later builds; the personal toolbar folders can not be opened in new windows. But if i middle-mouse click them, all content in the folders opens in new tabs. That was earlyer reported as bug 307115, resolved as WFM without pointers to the fix.
Comment 8•19 years ago
|
||
Sounds like bug 304563 to me.
Assignee: general → guifeatures
Component: General → XP Apps: GUI Features
Flags: blocking-seamonkey1.0a?
QA Contact: general
Comment 10•19 years ago
|
||
removing blocking-seamonkey1.0a request. Please only re-request if that can be confirmed in branch builds as well, which I seriously doubt as autoscroll hasn't landed on trunk, IIRC...
Flags: blocking-seamonkey1.0a?
Comment 11•19 years ago
|
||
re-requesting, since autoscroll has branch approval and presumably will land there and I really don't have the time to watch the branch for it.
Flags: blocking-seamonkey1.0a?
Comment 12•19 years ago
|
||
Is this as simple this change in contentAreaClick.js (based on attachment 194451 [details] [diff] [review])? if (event.button == 1 && !hrefAndLinkNodeForClickEvent(event) - && (!pref || !pref.getBoolPref("middlemouse.contentLoadURL")) + && (!pref || !pref.getBoolPref("middlemouse.contentLoadURL") || + !pref.getBoolPref("middlemouse.scrollbarPosition") || + !pref.getBoolPref("middlemouse.paste")) && (event.target != event.currentTarget)) {
Comment 13•19 years ago
|
||
Assigning to CTho. Chris, see the above suggestion.
Assignee: guifeatures → cst
Comment 14•19 years ago
|
||
bz, in this case moving to beta, as alpha has been tagged and autoscroll is not in that one.
Flags: blocking-seamonkey1.0a? → blocking-seamonkey1.0b?
Comment 15•19 years ago
|
||
Wouldn't that disable autoscroll altogether if those prefs are set? I'd think that for middlemouse.scrollbarPosition we want to autoscroll as long as it's not a scrollbar being clicked on...
| Reporter | ||
Comment 16•19 years ago
|
||
i found that a pref for disabling autoscroll was addedin Firefox already 2 years ago. Perhaps something there worth looking at: bug 212000. It would be highly annoying not to be able to get rid of it alltogether..
Comment 17•19 years ago
|
||
Toolkit has isAutoScrollBlocker in browser.xml. Isn't this what we're looking for? http://lxr.mozilla.org/mozilla/source/toolkit/content/widgets/browser.xml#689
| Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 18•19 years ago
|
||
I'm not sure what the "scrollbarPosition" pref does (make scrollbars act like they do in weird old X apps?). I can't seem to detect when you middle click on a scrollbar (the FF code doesn't work for me), and the scrollbars don't show up in DOMI, so I don't know how to handle the scrollbar stuff. The middlemousepaste is easy to fix, but it'll have to wait until I can get info about scrollbarPosition. Clearing the blocking? flag. I won't land any autoscroll on branch unless this is fixed, so blocking+ would be blocking for a feature, which I'm told we don't do.
Flags: blocking-seamonkey1.0b?
Comment 19•19 years ago
|
||
(In reply to comment #17) >Toolkit has isAutoScrollBlocker in browser.xml. Isn't this what we're looking for? Roughly, but incorrect for xlinks and arbitrary input elements - you can tell which because pastable inputs have controllers, and you could even use target.controllers.getControllerForCommand('cmd_paste').isCommandEnabled('cmd_paste') to see if there is anything to paste (into). (In reply to comment #18) >I'm not sure what the "scrollbarPosition" pref does (make scrollbars act like >they do in weird old X apps?). Have you not shift-clicked a scrollbar recently (gecko or w2k+)? (For more fun in w2k+ try right-clicking a scrollbar.) >the scrollbars don't show up in DOMI No, but they will still be the original target of mouse event - you should see one of scrollbarbutton slider thumb or scrollcorner. You can find a scrollbar in DOMI by inspecting a XUL tree (or write your own scrollbar testcase).
| Assignee | ||
Comment 20•19 years ago
|
||
Fixed by second checkin for bug 304563.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•