-
Notifications
You must be signed in to change notification settings - Fork 975
When maximized, hitboxes seem off for buttons and address bar #7641
Comments
It seems the refresh button also does this. |
I just noticed that it might be related to the window state. When I have Brave maximized this occurs, but if I leave Brave windowed I can click the buttons without the aforementioned problem. |
I can reproduce the issue with the window maximized. @bsclifton would you please check it out? as it seems to me to be related with the title bar |
@jonathansampson reported that not all of the URL bar area is clickable. I think these issues are related.
|
@luixxiul It's definitely related to this issue, because I've also had trouble clicking the address bar while Brave is maximized. I forgot to mention that in my last reply, but it's good someone else caught it. |
I just noticed that the little lock for HTTPS is nigh impossible to click while the window is maximized. I'm assuming this is related to the current issue, so I thought I'd mention it. |
+1 from users @chubbyninja and @hexigen via #8176 |
My hunch is that this problem is in the Electron/Muon code. The client rect is likely wrong because of border calculations. The fixes I have in mind should also fix #5159 My first step would be to pull in electron/electron#9140 from upstream electron into Muon |
@bsclifton according to http://dpi.lv/ it's 170 DPI scaling would be 100% as i have not altered anything like that, hope this is helpful and goodluck! |
FYI I have noticed the wrong non-clickable areas behave like the title frame, i.e. a double click on what should have been a UI element (like the url bar) instead restores the window to non-maximized state. The same happens with the timing information (little blue text) embedded inside the right side of the address bar, but this may be intended (wrong choice IMHO) and unrelated to this bug since it happens in both maximized and restored window states. This drives me crazy. :) |
- manually applied: electron/electron@638eae1 - manually applied: https://github.com/electron/electron/pull/9167/files Passes the correct subsystem variable to linker. Before, older Windows version was being used which affected GetSystemMetrics (wrong values returned) Should fix brave/browser-laptop#7641 Should fix brave/browser-laptop#7215 Might fix brave/browser-laptop#5159 Auditors: @bbondy, @bridiver
- manually applied: electron/electron@638eae1 - manually applied: https://github.com/electron/electron/pull/9167/files Passes the correct subsystem variable to linker. Before, older Windows version was being used which affected GetSystemMetrics (wrong values returned) Should fix brave/browser-laptop#7641 Should fix brave/browser-laptop#7215 Might fix brave/browser-laptop#5159 Auditors: @bbondy, @bridiver
Also happens with tab sets: #8292 |
Comfirmed fixed in latest master 👍 |
Test plan
Original issue description
covering both:
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Clicking the back or forward buttons didn't seem to work consistently. I discovered that clicking near the edge was not working. I had to click in the very center of the button. It seems that the clickable area of the button is not the whole button.
Platform (Win7, 8, 10? macOS? Linux distro?):
Win7 64
Brave Version (revision SHA):
1db81cb
Steps to reproduce:
Actual result:
Clicking the button works if you click nearer to the center.
Expected result:
The button should work if you click it anywhere in the graphical button.
Will the steps above reproduce in a fresh profile? If not what other info can be added?
I believe so. I've just installed Brave.
Is this an issue in the currently released version?
Yes
Can this issue be consistently reproduced?
Yes
#5679
The text was updated successfully, but these errors were encountered: