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

Docs: Updated snippet styles to the latest nested editable CSS class naming convention #917

Merged
merged 5 commits into from
Mar 30, 2018

Conversation

oleq
Copy link
Member

@oleq oleq commented Mar 21, 2018

Suggested merge commit message (convention)

Docs: Updated snippet styles to the latest nested editable CSS class naming convention (see #578).


Additional information

Requires: ckeditor/ckeditor5-widget#36

@Reinmar
Copy link
Member

Reinmar commented Mar 23, 2018

WDYT about this change after making it? Does it make sense to use the same class for root and nested editables? Or does it bring more issues than it needs to do?

@@ -74,12 +74,12 @@ It breaks CKEditor 5 (see how <p><code>[]</code></p> looks). */
padding: 0;
}

#snippet-inline-editor .ck-editor__editable {
#snippet-inline-editor .ck-editor__editable:not(.ck-editor__nested-editable) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we use .ck-content here? It would pick just the right element. And kinda makes sense semantically too, doesn't it? You want to align the style of the editor contents so it looks well.

@Reinmar
Copy link
Member

Reinmar commented Mar 23, 2018

Before you'll answer, please also see https://github.com/ckeditor/ckeditor5/pull/917/files#r176673884.

@oleq oleq requested a review from szymonkups March 28, 2018 10:03
@oleq
Copy link
Member Author

oleq commented Mar 30, 2018

WDYT about this change after making it? Does it make sense to use the same class for root and nested editables? Or does it bring more issues than it needs to do?

TBH, I haven't seen any issues. It definitely fixes all the issues caused by Grammarly, though.

@szymonkups szymonkups force-pushed the t/ckeditor5/578 branch 4 times, most recently from 76c29c9 to e97c33d Compare March 30, 2018 09:30
@szymonkups szymonkups merged commit 843da25 into master Mar 30, 2018
@szymonkups szymonkups deleted the t/ckeditor5/578 branch March 30, 2018 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants