Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
theme system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Oct 2014 at 12:23 UTC
Updated:
20 Feb 2015 at 17:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
emma.mariaComment #2
emma.mariaI have copied the templates over to classy and removed the classes from the original module templates. There is CSS left in the module that reference the removed classes so a follow up is needed - tagged cssbanana.
Comment #3
derheap commentedComment #5
derheap commentedWe should remove all classes, but attributes should still be printed.
Otherwise RDF and other things can break.
{{attributs}} should still be printed.
{{tip.attributes}} should still be printed.
{{item.attributes}} should still be printed.
{{attributes}} should still be printed.
Comment #6
mortendk commentedComment #7
runand commentedComment #8
runand commentedComment #10
davidhernandezPlease double-check if any removed classes are being used in javascript. It is best to test the affected template using Stark to make sure nothing is broken.
Comment #13
xen commentedComment #14
xen commentedChecked the JS files using Stark:
filter.filter_html.admin.js
- Checked that the "Allowed HTML tags" text field got updated when dragging the sup button into the CKEditor toolbar, and that the description explained that the tag was added.
filter.admin.js
- Checked that the settings for a configurable filter was properly shown and hidden when toggling the checkbox.
filter.js
- Checked that the format description changed when changing text format on a new article.
Everything worked the same on Bartik and Stark.
The failures of the testbot is differences in classes on some elements, but I believe that the bot should now test using Classy as a theme, so I'm requeing.
Comment #15
xen commentedComment #18
davidhernandezThe test failures on the first group are unit tests that are checking for exact markup. We can probably just remove the classes from the test, as they don't appear to be relevant to the individual tests.
The main issue is those align-left, align-right, align-center classes might be considered functional, and it is exactly what those tests are checking for. Is it odd that it is a unit test and not a web test (which is why it is failing)?
If those classes are considered functional, we shouldn't remove them. Opinions?
Comment #19
xen commentedGrepping for the classes finds them in system.module.css.
I'd call them functional.
It does make some kind of sense that it's unit tests. It's testing the filtering function, and as little as possible else. That there's a bit of templating involved is a minor detail.
Comment #20
xen commentedRemoved the classes from the test, apart from the align classes.
Re-introduced adding classes to the module filter-caption.html.twig, so the align classes will get properly added.
The interdiff seems a bit odd, I think git is to clever for it.
Comment #22
mortendk commentedThe css needs to have classnames renamed so it follow the oocss doc standards.- that work can first be done when everything is moved over and should be a followup issue.
filter.caption.css contains elements that are essential for the functionality, and should be trated as such.
Comment #26
davidhernandezComment #27
davidhernandezIn filter-guidelines 'format.name' changed to 'format.label'. That was the only change.
<h4 class="label">{{ format.label }}</h4>Comment #29
davidhernandezHad to remove the class from tests.
Comment #30
mortendk commentedok good from here
Comment #31
webchickCommitted and pushed to 8.0.x. Thanks!