froala / wysiwyg-editor

The next generation Javascript WYSIWYG HTML Editor.
https://www.froala.com/wysiwyg-editor
Other
5.28k stars 672 forks source link

IMPORTANT! Enter -key causes inline editor to jump view position, editor pretty much useless #4229

Open manttih opened 3 years ago

manttih commented 3 years ago
Expected behavior.

When using inline editor, pressing of ENTER -key should keep the view where the cursor is.

Actual behavior.

When the editor size is bigger than viewport, the view jumps to top. This renders the editor pretty much useless, and this should be TOP PRIORITY fix.

Steps to reproduce the problem.

Go to https://froala.com/wysiwyg-editor/inline/. Click Enter enough times and scroll to cursor position. Keep pressing enter, and the view will jump to top.

Editor version.

3.2.6

OS.

Windows 10

Browser.

All I've tested (Firefox, Chrome, Edge, Opera)

Recording.

https://user-images.githubusercontent.com/14157080/117773422-f56acb80-b240-11eb-8645-8641b93bfcc0.mp4

manttih commented 3 years ago

The problem persists on 3.2.7.

idengager commented 3 years ago

And here I was thinking it was an issue with our app 😬 Please fix this, it's a major problem that our users report. We experience this as well on v3.2.6-1 (via angular-froala).

manttih commented 3 years ago

The problem STILL persists on 4.0.1. This is a HUGE problem - even though some of our clients have moderate amount of text, lots of them use large fonts / line-heights so a basic, couple column cell causes the editor to jump on top of the page on EACH enter click (which is beyond annoying, espeacially if there are banners or other content before the editor).

AkshayCM commented 2 years ago

Thank you for your feedback. The request has been reported to the product management team for evaluation and consideration for an upcoming release.

gerritvds commented 2 years ago

We're also experiencing this issue on version 4.0.13.

brookeeeburton commented 9 months ago

We're still experiencing this as well on 4.1.2!

MnichMaciej commented 2 months ago

We're still experiencing this on 4.2.1!