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

Selection started from a nested table causes an error in a browser while scrolling down #493

Closed
Comandeer opened this issue Jun 9, 2017 · 0 comments
Assignees
Labels
plugin:tableselection The plugin which probably causes the issue. status:confirmed An issue confirmed by the development team. type:bug A bug.

Comments

@Comandeer
Copy link
Member

Are you reporting a feature or a bug?

Bug

Check if the issue is already reported

https://dev.ckeditor.com/ticket/17052

Provide detailed reproduction steps (if any)

  1. Create a 5x5 table (editor should become scrollable).
  2. In the first cell make 2x2 nested table with width set to 15.
  3. Fill every cell with letter "s".
  4. Start selection from nested table, then move it out of the table and drag it to scroll down the editor.

Expected result

Selection should stay in a nested table without returning any errors in console.

Actual result

There is an error in a console. ​https://gist.github.com/Mgsy/b5c95910313a7cb70e87beae921ac74f

Other details

  • CKEditor version: 4.7.0
  • Installed CKEditor plugins: tableselection
@Comandeer Comandeer added plugin:tableselection The plugin which probably causes the issue. status:confirmed An issue confirmed by the development team. type:bug A bug. labels Jun 9, 2017
@Comandeer Comandeer self-assigned this Jun 9, 2017
@mlewand mlewand changed the title Selection started from nested table causes an error in a browser while scrolling down Selection started from a nested table causes an error in a browser while scrolling down Jun 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugin:tableselection The plugin which probably causes the issue. status:confirmed An issue confirmed by the development team. type:bug A bug.
Projects
None yet
Development

No branches or pull requests

1 participant