Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect work area calculation web (WASM) on android #14452

Closed
AlexeyTliss opened this issue Feb 2, 2024 · 0 comments · Fixed by #14899
Closed

Incorrect work area calculation web (WASM) on android #14452

AlexeyTliss opened this issue Feb 2, 2024 · 0 comments · Fixed by #14899

Comments

@AlexeyTliss
Copy link

AlexeyTliss commented Feb 2, 2024

Describe the bug

When opening web application (Avalonia.Browser) from android-based mobile device on chromium browsers (Chrome, Edge, Opera) avalonia application doesn't calculate work area correctly, seemingly not taking into account browser's tool area (adress textbox, tabs) into account, and not substracting browser's tool area rect from work area rect. As a result, some of content is out of window bounds.

To Reproduce

Host browser version of application on any machine by any means (direct, nginx, apache)
Go to application web adress from any mobile android device (preferebly not emulator)
See error: page size is calculated incorrectly and there is no footer (see screenshots)

Expected behavior

All of page content is fit into a browser window on mobile android device

Screenshots

1: Desktop browser: no bug, footer is clearly visible NoBug
2: Android tablet, horizontal mode: footer is missing bug1
3: Android tablet, vertical mode: footer is missing
bug2

Environment

  • Source code: Issue_Android_WASM_Incorrect_WorkArea.ZIP
  • Device 1: Samsung Galaxy Tab Active3, Android 13, 1920х1200, Chrome Browser
  • Device 2: Oukitel RT7 TITAN 5G, Android 13, 1200х1920, Chrome Browser 120.0.6099.193, Yandex Browser 23.9.6 build 84
  • Most likely reproduces on any similar physical device
  • Avalonia-Version: 11.0.0, Net7

Update:
Same on IPad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants