Details
-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: 2015.11.2
-
Fix Version/s: QA tracked issues, 2015.12
-
Component/s: Platform UI (Admin UI & Content UI)
-
Labels:
-
Environment:
Operating System: Debian 8
PHP Version: 5.6.14-0+deb8u1
Database and version: Mysql 5.5.46-0+deb8u1
Browser (and version): Firefox 42
Description
Steps #1
- Create a content that have two a richtext fields
- Access the first fieltype
- The richtext toolbar opens
- Now access the second richtext toolbar
- the Richtext toolbar from the second field open, but the toolbar from the first also remain opened
Steps#2
- Create a content that have a richtext fields
- Access the fieltype
- The richtext toolbar opens
- Click on "Focus" button
- The richtext toolbar remain in the middle of the screen
Issue Links
- relates to
-
EZP-25235
Upgrade to AlloyEditor 0.7
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
+1 on applying the fix only. And we can aim to update to newer version for 1.0.1.
Show
André Rømcke
added a comment - +1 on applying the fix only. And we can aim to update to newer version for 1.0.1.
OK, I'll do the "custom 0.6" version.
The upgrade to 0.7 should be quite easy basically we need to put 0.7 in PlatformUIAssetsBundle and fix a few deprecation warnings because of the new React version bundled with it.
Show
Damien Pobel (Inactive)
added a comment - OK, I'll do the "custom 0.6" version.
The upgrade to 0.7 should be quite easy basically we need to put 0.7 in PlatformUIAssetsBundle and fix a few deprecation warnings because of the new React version bundled with it.
Same opinion than André.
Show
Bertrand Dunogier
added a comment - Same opinion than André.
So I created an eZ Systems AlloyEditor version 0.6.1 which basically the 0.6.0 version + those 2 patches. This version is embed in PlatformUIAssetsBundle 1.0.0-rc2
Show
Damien Pobel (Inactive)
added a comment - So I created an eZ Systems AlloyEditor version 0.6.1 which basically the 0.6.0 version + those 2 patches. This version is embed in PlatformUIAssetsBundle 1.0.0-rc2
Tested and approved by QA for master.
Show
Rui Silva (Inactive)
added a comment - Tested and approved by QA for master.
This appears to be a bug in AlloyEditor itself https://github.com/liferay/alloy-editor/issues/371
This bug is fixed in AlloyEditor 0.7 (we are using AlloyEditor 0.6) and it is actually fixed in https://github.com/liferay/alloy-editor/commit/e2a85401c669df27e386d912bc2bb440c4cf8e83 (and improved in https://github.com/liferay/alloy-editor/commit/1288cec9035a47469c085244fc95c982822945cb). It's way to late to upgrade to v0.7 but maybe, we can ship a modified 0.6 version in PlatformUIAssetsBundle with those 2 fixes.
Bertrand Dunogier André Rømcke any opinion on that ?