Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Sub-issue of #1190252: [573] Use csslint as a weapon to beat the crappy CSS out of Drupal core
Inline with the CSS cleanup efforts of the HTML5 initiative, using CSSLint at http://csslint.net provides a quick way to code-sniff our css and tweak styles.
Files:modules/ckeditor/ckeditor.admin.css and ckeditor-iframe.css
Proposed resolution
Clean up css in ckeditor module
- Copy and paste the the stylesheet(s) below into the css lint tool at http://csslint.net and test.
- Fix any warnings or errors the tool finds.
- Patch Drupal 8 locally and make sure the css changes have not broken anything visually.
- Create patch and upload for the testbot.
Remaining tasks
User interface changes
Should be no difference between before and after.
Before
After
API changes
Beta phase evaluation
Issue category | Task because coding standards |
---|---|
Issue priority | Not critical because it causes no errors |
Unfrozen changes | Unfrozen because it only changes CSS |
Comment | File | Size | Author |
---|---|---|---|
#1 | ckeditor-css-cleanup-2470617.patch | 2.73 KB | majmunbog |
#1 | ckeditor_d8.png | 30.18 KB | majmunbog |
#1 | ckeditor_d8_after-photo.png | 139.11 KB | majmunbog |
#5 | ckeditor-article-after(Chrome).png | 41.28 KB | Manjit.Singh |
#11 | after.png | 362.55 KB | _nolocation |
Comments
Comment #1
majmunbog CreditAttribution: majmunbog commentedPatch and screenshots added.
Comment #2
majmunbog CreditAttribution: majmunbog commentedComment #3
Manjit.SinghSeems fine from myside, No issues found in CSSlint. :)
Comment #4
LewisNymanNice! All we need now are some before/after screenshots to show there are no changes.
Comment #5
Manjit.SinghFound no issues in Ckeditor :)
Comment #6
MathieuSpil CreditAttribution: MathieuSpil commentedTested the patch manually, it looks great!
Extra: I noticed that since #1872206: Improve CKEditor toolbar configuration accessibility, we are no longer using the
.ckeditor-row-controls
-class. And because that ticket was fixed for over a year ago. We can assume that this is not being used anymore.So based upon patch in #1, I removed some unused styling:
@Manjit: Be sure to also check this page: /admin/config/content/formats/manage/full_html, there is a lot of the changes that happened there.
Comment #7
LewisNymanThis is looking good :) I can't see any CSSlint errors, now we just need some screenshots before/after the patch.
Comment #8
LewisNymanSpecifically, we need before/after screenshots of: /admin/config/content/formats/manage/full_html
Comment #9
_nolocation CreditAttribution: _nolocation commentedComment #10
Manjit.Singh@MathieuSpil everything is fine on
/admin/config/content/formats/manage/full_html
:) Can you please paste the screenshots where you find some changes due to latest patch.Comment #11
_nolocation CreditAttribution: _nolocation commentedScreenshots taken on OS X Chrome Version 41.0.2272.118
Looks good to me.
Comment #12
_nolocation CreditAttribution: _nolocation commentedComment #13
YesCT CreditAttribution: YesCT commented@_nolocation thank you for doing the screenshots.
Next time, please embed the screenshots in the issue summary in the UI changes section of the issue summary template (the http://dreditor.org browser plugin helps make that easier). See also https://www.drupal.org/contributor-tasks/add-screenshots
I put the screenshots in the issue summary.
Comment #14
YesCT CreditAttribution: YesCT commentedRemoving the needs screenshot tag. Everything else looks good and @LewisNyman ok'd this earlier.
Comment #15
YesCT CreditAttribution: YesCT commentedComment #17
webchickCommitted and pushed to 8.0.x. Thanks!
Congratulations to trboslav for their first commit mention! :D
Comment #18
webchickStill haven't had coffee yet. ;)
Comment #19
Wim LeersThanks for the clean-up! :)