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:25 UTC
Updated:
20 Feb 2015 at 13:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mortendk commentedmoved the classes out of core + all template files copied over
Discussion of the classes - should be done as a follow up, so bikesheedding wont stop classy ;)
Comment #2
mortendk commentedgo bot go
Comment #3
davidhernandezThe templates should go into the root of the templates folder, not a subfolder.
Comment #4
lauriiiAre we really gonna remove styles from divs also? I thought classy is only about classes
Comment #5
derheap commentedThe style attributes have to stay: they are necessary for the preview.
Comment #6
mortendk commentedyup they are nessesary and thats why they are in classy - but not in the core.
Comment #7
runand commentedComment #8
runand commentedComment #9
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 #10
rainbowarrayI think derheap has a good point. These are the templates to generate previews of how image styles will look, right? That still has to work in themes that are using Core instead of Classy without every theme manually re-implementing that.
Comment #11
rainbowarrayAlthough now that I'm thinking about it, an image style preview would be showing up in Seven, which is based on Classy, so this is maybe fine.
Comment #12
lauriiiI dont think we should break functionality with classy
Comment #13
davidhernandezThe style attributes should stay in core as well as Classy. It is part of the functionality of the the template.
Comment #14
mortendk commentedok well then lets have a follow up issue on this & get it moved over without removing the inline styles.
Comment #15
lauriiiUnremoved style attributes
Comment #16
mortendk commentedto prevent disucssion about if inline styles are preferable in a template i have removed that from the patch, we can do that as a followup instead .
Comment #17
lauriiiCould you provide interdiff?
Comment #18
davidhernandezIf those are copied files without changes, please check your git settings. https://www.drupal.org/documentation/git/configure . The section on "Optimize diffs for renamed and copied files".
Comment #20
lewisnymanDo we want to remove these empty divs and spans in the module template files?
Comment #21
mortendk commentedWe should do that as followup's lets get the templates into classy first, then we can clean up core even more if theres a need for that
Comment #22
davidhernandezWhy wouldn't the empty divs be removed? I'm pretty sure we've done that in other issues?
Comment #23
davidhernandezand also try to avoid follow ups as much as we can.
Comment #24
lewisnymanI took some screenshots before and after. It looks like the image style preview functionality is broken in core or is it just me?

Comment #25
mortendk commented@david - didnt we end up in never ending bikesheds when we tried to do tomuch ?
keeping those things to followups, makes it easier for us to move stuff into classy & not beeing borked down.
Im pretty sure we did that on other issues before, but if its not gonna be suddenly blockers, then yes for all sake lets clean as much as possible :)
Comment #26
davidhernandezI thought we did, but now I don't know. I'll look through the previous ones to see what we decided.
Comment #27
davidhernandezI think you're right. The other ones left empty divs, so we must have left that for "dream markup". Ignore me, carry on.
Comment #28
lewisnymanOk thanks for the replies. I can confirm that the image style styling is broken in HEAD so we need to open a new issue], not fix it here.
Comment #29
alexpottThis bit from the IS does not seem to have been done.
Comment #30
manuel garcia commentedI have greped core for the classes that we are removing from image module templates, which are:
There are no JS files in core that make use of any of these css classes that I could find.
As far as CSS goes, the ones I found are all in the module's CSS files:
image.admin.cssandimage.theme.css. Please note that I ignoredclearfixclass because this is just a helper class.On image.admin.css:
These are used (moved to classy in the patch)
On image.theme.css:
These are used:
These are NOT used anywhere (should be safe to remove)
Comment #31
mortendk commentedill set this back to rtbc - we are not cleaning out css nor are we yet moving css over.
Anyways templates are ready to be moved, css have been discussed & we have an overview :)
Comment #32
alexpottTemplates changes are not blocked during beta. Committed 16d3e1c and pushed to 8.0.x. Thanks!