-
Notifications
You must be signed in to change notification settings - Fork 60
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
EZP-29328: As a editor I want OE to support formatted text #676
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
4af7c26
to
f8d0b96
Compare
Updated* and rebased, so ready for review. * Removed webpack changes not relevant, needed to keep changes in all toolbars where option for formatted is shown, they change because of the change in |
constructor(config) { | ||
super(config); | ||
|
||
this.name = 'paragraph'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably not a paragraph
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed :)
'ezmoveup', | ||
'ezmovedown', | ||
this.getStyles(config.customStyles), | ||
// NOTE: alignment currently not supported on <pre> so skipping buttons for that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vidarl Actually did not check if this is supported or not on pre/programlisting, besides noticing there where no handling of this in the xsl. However if we did not have it in legacy either there is probably no need to add it on formatted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not have align in legacy ( editor disables align buttons ) on literal.
Docbook does not support it on ProgramListing either, but we are free to add support for ezxhtml:align
attribute if we choose to.
However, since it was not a need for it in legacy, it is likely no needed now either.
@dew326 updated 👍 Note that I have not added this to the "Add block" toolbar, I think we should, but then we probably need a new icon for it and I'm unsure how you guys do that now. |
OK, let's move it to QA, we could make 2.3.1 on Friday as I have some other fixes in the pipeline. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
During the tests I noticed several bugs on different browsers. For other blocks they don’t occur.
Cursor appears in the block frame only when you start to write.
Safari:
After switching to Formatted toolbar skips.
Chrome:
For more text, scroll appears in edit mode. If clicking Add button in situation when cursor is outside the current view, page and toolbar skips.
@katarzynazawada which of these issues are unique to the change here? As in, safari issue and chrome add button issue sounds like its unrelated => generic that might also happen with edge cases on other blocks, or? The Firefox and the chrome scroll bar issues are probably due to |
@katarzynazawada If you have those browsers still running, could you cross check against https://alloyeditor.com/ ? (front page, scroll down to "In live demo, click/touch here") |
@andrerom I’ve checked these issues again both on master and your branch. From my observations, all of them only appear for Formatted block. What is more, on Chrome, there is one more case:
|
Besides being new feature in eZ Platform, this allows migration of plain literal tags to eZ Platform, as recently added in migration script.
1f7f530
to
3b1d640
Compare
Pushed CSS that tries to solve some of the issues. @lserwatka btw some of those seems fixed in Alloy 1.5.x: liferay/alloy-editor#867, liferay/alloy-editor#868, liferay/alloy-editor#888 @dew326 do you have suggestion on what might cause the remaining toolbar issue on empty tag? I see Alloy adds a br inside paragraphs which is probably to avoid this, anyway we can emulate that in CSS too? |
3b1d640
to
dd3e1e5
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
On closer look the toolbar issue here is not caused by Alloy, as it's our own toolbar. Code responsible for remaining set of toolbar position bugs is |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@katarzynazawada Added fix for:
You should not need to update Alloy for this, in the end the bugs where caused by our code, so you don't need new asset package to test this. For devs: |
@andrerom After fixes I noticed some issues:
Toolbar skips: A)
See movie: http://recordit.co/tsiwhvKKza B)
Placeholder sometimes disappears
After publishing ,in Content item view, there is a blank space in field instead of This field is empty text
Pre use scroll is not added.
|
@SylvainGuittard If you want this feature, please get someone else to take over at some point. The level of deep issues in Alloy / browsers here is beyond what I have time to reverse engineer any time soon. |
UPDATE: Placeholder issue was fixed in branch here in 45feb2f (by removing placeholder, it's not important). However the toolbar issue is something else, maybe deeper in the editor, so if we want to cover all edge cases on first try here, it's better if a frontend guy can dig into it. /cc @lserwatka |
Besides being new feature in eZ Platform Admin UI, this allows migration of plain literal tags to eZ Platform as supported since 2.3.0 in kernel and migration scripts. This is why this is suggested for 1.3.1, to avoid customers reporting it as bug once they migrate.
Checklist:
$ composer fix-cs
)