[MGNLUI-5604] CKEditor: Assets chooser opens in background and can't be accessed Created: 14/Jan/20  Updated: 04/Jan/21  Resolved: 04/Jan/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.1.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-01-14 at 14.22.08.png     PNG File Screenshot 2020-12-28 at 12.25.31.png     PNG File missing-button.png    
Issue Links:
causality
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Our customer has found same bug than MGNLUI-5018 when using CKEditor from a content app form instead of within a component dialog.

Steps to reproduce using our demo (tours app):

  1. Set images to true in /ckeditor/config-magnolia.js (line l14) in order to be able to use image browser plugin
  2. In configuration app, add configJsFile property with value /.resources/ckeditor/config-magnolia.js to /modules/tours/apps/tours/subApps/detail/editor/form/tabs/tour/fields/body
  3. When opening the edit tour form and press image button in the CKEditor, the asset chooser will be placed background and won't be editable:

This doesn't happen when CKEditor is placed within a dialog, for example when using it within a component in pages app (that's what was fixed in MGNLUI-5018)



 Comments   
Comment by Richard Gange [ 01/Jul/20 ]

On 6.2.1 the button seems to be missing.

Comment by Richard Gange [ 01/Jul/20 ]

Inspecting the element I find it's intentionally being hidden.

Comment by Jonathan Ayala [ 28/Dec/20 ]

In 6.2.5 it works fine:

 

Generated at Mon Feb 12 09:28:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.