search

getkirby / kirby

Kirby's core application folder
https://getkirby.com
Other
1.32k stars 168 forks source link

Topbar and Noticebar (unsaved changes) disappear on mobile Browsers (iOS Safari, iOS Chrome) while editing #4172

Closed teichsta closed 1 year ago

teichsta commented 2 years ago

Description

(as discussed here https://forum.getkirby.com/t/topbar-and-noticebar-unsaved-changes-disappear-on-mobile-browsers-ios-safari-ios-chrome/24794?u=teichsta)

When using kirby panel on mobile devices (e.g. iPhone or iPad) the Top- und Noticebar appearance is inconsistent. Sometimes the bars disappear when entering a textarea field (but sometimes not). Once the bars disappeared there is no chance to scroll to them again (as long as the editor is activ). After leaving the editor the bars appear again.

Expected behavior
Both bars shall be visible at any time. Otherwise the editor is not aware of his changes and the need to save these changes to the server.

Screenshots

image

It seems that two scrollbars are active at the same time:

image

Observed in that context: Sometimes the toolbar of the textarea remains fixed while scrolling (see screenshot, also see the cursor which still is shown while scrolling)

image

To reproduce

Add a textarea to your page blueprint and enter the edit mode. The virtual keyboard appears and the bars disappear (or not). Once the bar disappear you will be able (with some hassle and touching on the outer right border) to make a second scrollbar appear which seem to scroll the entire viewport. If you manage to touch this second scrollbar you are able to scroll to either top and noticebar (unsaved changes).

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. This is for us to prioritize issues that are still relevant to our community. It will be closed if no further activity occurs within the next 14 days. If this issue is still relevant to you, please leave a comment.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. This is for us to prioritize issues that are still relevant to our community. It will be closed if no further activity occurs within the next 14 days. If this issue is still relevant to you, please leave a comment.