We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is a small UI bug since it truly can break the flow.
Originally posted by @erredeco in #270 (comment)
... it changes the appearance of the page...
So we have to avoid:
As example we could move (copy) the content with javascript and append after the wrapper:
<div style="content: none;" class="cke_editable cke_editable_inline"> <p>...</p> <p>...</p> </div> <p data-cid="some-uid">...</p> <p data-cid="some-uid">...</p>
Or we can move the inline-action wrapper inside the content layout with an new ViewHelper:
ViewHelper
<div id="c1" class="frame frame-default frame-type-text frame-layout-0"> <div class="t3-frontend-editing__ce> <span class="t3-frontend-editing__inline-actions">...</span> </div> ... </div>
This would prevent design problems, since the integrator can decide were it should appear.
Any opinions?
The text was updated successfully, but these errors were encountered:
@Messj1 This sounds like an awesome idea, go for it!
Sorry, something went wrong.
@Messj1 maybe you would like to add an opinion to #537?
No branches or pull requests
There is a small UI bug since it truly can break the flow.
Originally posted by @erredeco in #270 (comment)
So we have to avoid:
As example we could move (copy) the content with javascript and append after the wrapper:
Or we can move the inline-action wrapper inside the content layout with an new
ViewHelper
:This would prevent design problems, since the integrator can decide were it should appear.
Any opinions?
The text was updated successfully, but these errors were encountered: