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

Tooltips stop showing after the first editor is destroyed #12602

Closed
Dumluregn opened this issue Oct 7, 2022 · 0 comments
Closed

Tooltips stop showing after the first editor is destroyed #12602

Dumluregn opened this issue Oct 7, 2022 · 0 comments
Assignees
Labels
package:ui squad:features Issue to be handled by the Features team. type:bug This issue reports a buggy (incorrect) behavior. type:regression This issue reports a bug that was not present in the previous releases.

Comments

@Dumluregn
Copy link
Contributor

📝 Provide detailed reproduction steps (if any)

  1. Open the all-types manual test (http://localhost:8125/ckeditor5/tests/manual/all-types.html).
  2. Destroy the first editor (editors['#editor-classic'].destroy()).
  3. Hover over the button in another editor.

✔️ Expected result

Tooltip is visible.

❌ Actual result

Tooltips don't show up.

📃 Other details

This issue was initially found in GH Writer (ckeditor/github-writer#375).

For details see ckeditor/github-writer#375 (comment).

  • Browser: all
  • OS: all
  • First affected CKEditor version: 35.1.0
  • Installed CKEditor plugins: UI

If you'd like to see this fixed sooner, add a 👍 reaction to this post.

@Dumluregn Dumluregn added type:bug This issue reports a buggy (incorrect) behavior. package:ui type:regression This issue reports a bug that was not present in the previous releases. labels Oct 7, 2022
@mlewand mlewand added the squad:features Issue to be handled by the Features team. label Oct 10, 2022
@CKEditorBot CKEditorBot added the status:planned Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon. label Oct 10, 2022
@mateuszzagorski mateuszzagorski self-assigned this Oct 11, 2022
@CKEditorBot CKEditorBot added status:in-progress Set automatically when an issue lands in the "In progress" column. We are working on it. and removed status:planned Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon. labels Oct 11, 2022
@mlewand mlewand assigned oleq and unassigned mateuszzagorski Oct 12, 2022
@oleq oleq closed this as completed in 5809d20 Oct 14, 2022
@CKEditorBot CKEditorBot removed the status:in-progress Set automatically when an issue lands in the "In progress" column. We are working on it. label Oct 14, 2022
@CKEditorBot CKEditorBot added this to the iteration 58 milestone Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package:ui squad:features Issue to be handled by the Features team. type:bug This issue reports a buggy (incorrect) behavior. type:regression This issue reports a bug that was not present in the previous releases.
Projects
None yet
Development

No branches or pull requests

5 participants