Closed Bug 1263989 Opened 9 years ago Closed 9 years ago

Page would not scroll by mouse wheel when context menu is open

Categories

(Core :: Widget: Win32, defect)

48 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1265308
Tracking Status
firefox47 --- unaffected

People

(Reporter: alice0775, Unassigned)

References

Details

(Keywords: regression, ux-consistency)

After landing Bug 982121, page would not scroll by mouse wheel when context menu is open Steps To Reproduce: 1. Open web page 2. Right click on the page to open context menu 3. Attempt to scroll page with mouse wheel Actual Results: Page would not scroll Expected Results: Page should scroll
When I encounter the problem at first time, I thought my mouse wheel had broken :(
This seems like a feature rather than a bug to me? It's really weird that you can click in a text box, get a textbox context menu, and then scroll the page and have the textbox context menu just hover over the page as if that makes total sense, or as if it applies to the thing under the cursor. FWIW, OS X and Linux already behave this way (before bug 982121 landed). IE behaves the same way, too. Chrome dismisses its (non-native) context menus when you scroll.
Component: Layout → Widget: Win32
Yes, the mousewheel shouldn't have any effect when a context menu is open on Windows, as is the case with other applications.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Okay, Steps To Reproduce: 1. Open long web page 2. Open Bookmarks sidebar 3. Right click on a bookmark item to open context menu 4. Attempt to scroll page with mouse wheel I think in this case, page should be scrolled.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Other applications don't scroll in that case either.
(In reply to Neil Deakin from comment #5) > Other applications don't scroll in that case either. I know that. However, I think it is not the reason of WONTFIX. Because, Mozilla has been destroy the OS native look-and-feel after Australis, in-content preferences. And I do not like IE/Edge/Chrome behavior. that's why I use Firefox.
(In reply to Neil Deakin from comment #3) > Yes, the mousewheel shouldn't have any effect when a context menu is open on > Windows, as is the case with other applications. I don't see how this change is according to the plan. It's just one of those spontaneous regressions which were marked as WONTFIX. If it was a part of the plan regarding menus, you would fix: 1) Bug 1251981 2) Bug 1249064 So your attempt to justify this change as being consistent with other applications is logical failure (In reply to Alice0775 White from comment #6) > By the way, I do not like IE/Edge/Chrome behavior, that's why I use Firefox. GoogleChrome 49 is OK. It just hides contextmenu and allows to scroll page. Still better than Nightly
(In reply to arni2033 from comment #7) > (In reply to Neil Deakin from comment #3) > > Yes, the mousewheel shouldn't have any effect when a context menu is open on > > Windows, as is the case with other applications. > I don't see how this change is according to the plan. It's just one of those > spontaneous regressions which were marked as WONTFIX. If it was a part of > the plan regarding menus, you would fix: > 1) Bug 1251981 > 2) Bug 1249064 > So your attempt to justify this change as being consistent with other > applications is logical failure Neither of these has been marked wontfix, so there is no "inconsistency" or "logical failure". We cannot fix all the bugs all at the same time, and not all bugs get prioritized equally.
Bug 982121 is bug of Devtool and Options menulist. I think Fixing Bug 982121 should not affect content UX. And Devtool and Options UX bug should be low priority than content UX BUG. Bug 982121 should be backed out if it affect content UX.
(In reply to :Gijs Kruitbosch from comment #8) > Neither of these has been marked wontfix Hm, I thought that it was obvious that they'll end up either Wontfix or abandoned for decades. Even this "consistent" change appeared out of nowhere. If you say so, I am totally wrong here of course. It's just, in my understanding, if there's a plan indeed, there shouldn't be so huge time gaps between such changes, and good things like bug 1251981 shouldn't be in the very end of the list.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.