Button web example on bevyengine.org clickable area is wrong (Regression?)

[paul-hansen]

Bevy version

Whatever the examples are built with on the webpage: https://bevyengine.org/examples/ui/button/
Is not happening for me locally using Bevy 0.7

System information

Chrome Version 102.0.5005.63 (Official Build) (64-bit) on Windows 11

`AdapterInfo { name: "ANGLE (NVIDIA, NVIDIA GeForce RTX 3080 Direct3D11 vs_5_0 ps_5_0, D3D11)", vendor: 4318, device: 0, device_type: DiscreteGpu, backend: Gl }`

What you did

I opened https://bevyengine.org/examples/ui/button/ and tried clicking the button in the example.

What went wrong

The area that I can click the button is offset from the visual position of the button. It gets more offset (and maybe larger?) if the window is made smaller.

Additional information

Example:

video.mp4

I'm 90% sure this wasn't happening earlier today, so it might be something merged recently.

[paul-hansen]

I just tried pulling the main branch and running the example locally using cargo run --release --target wasm32-unknown-unknown --example button and it seems to be working correctly.
Depending on what version the website uses, this may already be resolved.

[benbot]

Yeah seems like @paul-hansen is right.
I'm seeing this same issue on the examples webpage (on firefox too, so a totally different browser), but not if i compile the lastest bevy example locally.

[mockersf]

Depending on what version the website uses, this may already be resolved.

The website is using the last released version, 0.7 here

[hymm]

This looks like it might be a duplicate of bevyengine/bevy-website#371 and should have been fixed by #4726.

[paul-hansen]

I agree that looks like the same thing and looks to be fixed in main now. Thanks for tracking that down 👍

I'll close this for now, feel free to reopen or anything though if you think something should be done before 0.8 releases.

[mockersf]

#4726 probably didn't fix this as it's an optional behaviour that is not enabled by default

[alice-i-cecile]

Reopened as we have a fresh reproduction.

[mockersf]

issue is on the CSS of the website changing the size of the canvas, I opened bevyengine/bevy-website#429 to change that