Respect device scale when calculating viewport bounds

[Sambhram1]

Scale all pointer coordinates and viewport bounds by before sending them to the backend. This ensures consistent coordinate spaces across the entire rendering pipeline.

[TrueDoctor]

@timon-schelling this is probably related to your upcoming work right?

[timon-schelling]

@timon-schelling this is probably related to your upcoming work right?

Yeah, I'm gonna test it with desktop later, maybe enough to set browser scale and apply this patch.

[timon-schelling]

@Sambhram1 are you still working on this? See CI for formatting issues.

And a note: Scale will also need to be respected by overlays. Feels sensible to do that in the same PR. I will probably do that tomorrow and merge this into that branch and give you co-author.

[Sambhram1]

@timon-schelling i will solve ci issue and push

[TrueDoctor]

@Sambhram1 you can npm run lint from the frontend directory and ideally either set up your editor to do this automatically, or set up a pre commit hook which runs the linter automatically before you commit

[TrueDoctor]

And you can also see the issues online in the diff viewer:

[timon-schelling]

!build

[github-actions]

📦 Build Complete for 8ed5b23
https://b21b9831.graphite.pages.dev

[timon-schelling]

This PR adds offsets to tools when browser zoom != 100%.

But this is essentially the conversion we need on desktop.

[timon-schelling]

Basically this solves the wrong issue. Scale not being applied for one tool, is fixed by scaling all coordinates, breaks other tools along the way.

@TrueDoctor We should decide if we want to work with logical or physical pixels in tools.

I will mark this as draft for now.

[TrueDoctor]

@Sambhram1 This did end up being a much bigger undertaking since there were many edge cases where the approach shown here did not give the correct results. This PR was thus ultimately superseded by this one: #3331 so I think this should be safe to close. So thanks a lot for your work, even tough it did not get merged in the end. Can you please test if this still fixes #3286 ?