Arrow keys cause the entire page to jump around, making the editor very difficult to use. It seems like the left arrow scrolls the current block to the top of the page, (EDIT: the right arrow does not scroll it down – I was confusing other Gutenberg scrolling) and the right arrow scrolls it down. This makes it super hard to edit the page.
Turns out there is a simple workaround: edit it while in tablet mode, or some other mode than 100% width. The problem entirely goes away, and all is well if you do that. So this is probably not worth looking into.
Step-by-step reproduction instructions:
Have a page whose length is longer than the browser window.
Shrinking the margins to use tablet mode doesn’t any longer work, because none of the dialog boxes show up when the margins are shrunk. So you can’t create links. So I’d like to increase the priority of this bug.
I don’t know if this helps, but adding the violentmonkey browser extension, and using it to override the CSS as follows partially fixes the problem. I’d prefer it eventually get fixed in Cwicly; grepping indicates the problematic style element gets added in index.js in the build directory of cwicly. Unsurprisingly, disabling all other plugins does not help. The violentmonkey script is below (edited to remove bogus color). This doesn’t totally help the scrolling, but it makes it a (little?) bit better.
Thanks for the report and sorry for not getting back on this one.
I’m not sure I am fully able to reproduce the issue you’re experiencing here.
Would you be able to take a quick screencast of this so that I can see what I might be missing?
I’ve also emailed you a temporary admin password so you can see it in action by editing the sample doc, or any other loooooong document (the negative EPS one also shows the behaviour). Hosting OS is linux, browser OS that shows the bug is Linux, but probably others…
No worries at all! You have an amazing platform, and I really love the passion you bring to it. This is soooooo much better than anything I’ve seen thus far!
Any ideas what might be going on? I’m happy to use post-browsing tools such as violentmonkey to monkeypatch the results into something that works better than the current, while waiting for a proper fix.