Brave screenshot Select Area cursor is offset/misaligned on Windows 11 after 1.95.101 update

Brave Browser Desktop Support
, ,
1

Description of the issue: Brave’s built-in screenshot tool (Ctrl+Shift+S) suddenly became misaligned today. When using Select Area, the screenshot selection/crosshair is offset from the actual mouse cursor position. It worked normally before today. Windows Snipping Tool (Win+Shift+S) works correctly.
How can this issue be reproduced?

  1. Open Brave.

  2. Open any webpage and press Ctrl+Shift+S.

  3. Choose Select Area and move the mouse to select part of the page. The screenshot selection/crosshair appears offset from the actual cursor position.

Expected result: The screenshot selection crosshair should align exactly with the mouse cursor.

Brave Version( check About Brave): 1.95.101

Additional Information: Operating system: Windows 11.
The problem started suddenly today after the recent Brave update.

Troubleshooting already attempted:

  • Restarted Brave using brave://restart
  • Reset page zoom with Ctrl+0
  • Tested on different displays
  • Tested graphics acceleration both ON and OFF
  • Relaunched Brave after changing graphics acceleration
  • Windows Snipping Tool (Win+Shift+S) works normally

Screenshot demonstrating the issue is attached.

image
image599×430 78.9 KB

2

i have the same problem did you find any sol?

3

I’m having the same issue. For troubleshooting purposes,

  1. Windows display scaling was tested at both 125% and 100%; the problem occurs at both settings.
  2. The issue occurs on every webpage.
  3. The issue also occurs in a newly created Brave profile.
  4. The issue also occurs in an Incognito window.
  5. Brave experimental flags were reset to their defaults.
  6. The screenshot feature previously worked correctly.
4

This is a known issue that we have logged here:

5

Same problems with misaligned screen copy on Windows 10 since recent update.

6

Why did they close the topic when they haven’t fixed the problem? It’s been a month or more and the issue still exists.

7

The issue is closed because the fix has already been submitted and is making it’s way to the release build.

8

Thank you

I hope they fix this problem in the new update because this solution on GitHub was just a temporary solution.

9

That wasn’t a solution – it was a just a suggested workaround in the issue thread. The way Github works (typically) is that issue reports are used to track status/behavior/reporting on a specific issue. The fix itself is contained in a pull request, which is linked to the original issue (and vice versa).

So the actual code fix (pull request) is here: