search

fabianmichael / kirby-markdown-field

Super-sophisticated markdown editor for Kirby 3, community built.
Other
160 stars 14 forks source link

[next] Vertical scroll position lost when unfocusing Firefox #115

Closed sebastiangreger closed 3 years ago

sebastiangreger commented 3 years ago

This happens on Firefox (both Linux and Windows, current version), but not on Chromium:

When editing a text longer than the screen height, the Panel's vertical scroll position gets lost when unfocusing the browser (e.g. switching to another application and then back). The view jumps to the top of the markdown field as the browser gets unfocused and remains there when switching back to the Firefox window.

The cursor, however, remains inside the markdown field and in the correct position and it is possible to resume typing after focus is back on Firefox -- after the first key stroke, the vertical scroll jumps back to put the current cursor position into view.

To reproduce:

Expected behaviour: The vertical scroll of the panel would not change when switching desktop focus to some other app (as it does in Chromium)

fabianmichael commented 3 years ago

@sebastiangreger Thanks for reporting the Bug, I can replicate it. But I’m currently kind of clueless about what’s causing this. There have been some weird bugs with the way how Kirby’s panel is setup, i.e. the main view is inside a scrollable container with position: absolute and transform: translateZ(0) set. But even after removing these properties and declaring the <html> element as scroll container, the issue persists.

Also tried to a minimal example, but that worked without any issues. Will investigate this further, once I have a chance to do so. Really don't want to force anyone into using Chrome. :-P

fabianmichael commented 3 years ago

@sebastiangreger As a Firefox user myself, this also annoyed me. I create some sort of fix by restoring the scroll position, when a blur event occurs. Not sure though, what’s the root cause of this issue. the Fixer plugin is only enabled for Firefox/Gecko engine and should do the trick. Please give it a try and let me know, if this solves your issue.

sebastiangreger commented 3 years ago

@fabianmichael Sorry this took so long: yes, I can confirm the issue appears to be solved (currently only based on a quick test run; I would follow up with you in case glitches appear in daily use later...)

Thank you for your efforts! The next version of this plugin is such a pleasure to work with :pray: