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.
See: #2405553: Ensure Seven's code is inline with the current standards
Remaining tasks
Review the current CSS — What to look for when reviewing CSS
User interface changes
None
API changes
None
Comment | File | Size | Author |
---|---|---|---|
#40 | interdiff_38-40.txt | 418 bytes | srilakshmier |
#40 | 2408473-40.patch | 11.13 KB | srilakshmier |
#38 | interdiff_2408473_37-38.txt | 5.31 KB | ankithashetty |
#21 | rtl-add-node.png | 110.62 KB | rudraram |
#19 | install-new-theme-form.jpg | 129.85 KB | manmohandream |
Comments
Comment #1
LewisNymanUploaded the css file so it can reviewed with Dreditor
Not really sure where to start here :P Maybe we can split up the file a bit more?
Comment #2
LewisNymanComment #3
joaogarin CreditAttribution: joaogarin commentedNot sure if you mean separating the file into two or three files (the file is a bit long). one suggestion would be :
form (form, fieldsets, fieldgroups, legends etc)
form-selects (specific to selects in forms)
form-inputs (input fields and textareas)
form-filters (filters)
form-states (some state specific styling for inputs and other elements such as :hover,:focus etc)
In terms of the selectors. Some of the elements like :
.form-disabled input.form-text,
.form-disabled input.form-tel,
.form-disabled input.form-email,
.form-disabled input.form-url,
.form-disabled input.form-search,
.form-disabled input.form-number,
.form-disabled input.form-color,
.form-disabled input.form-file,
.form-disabled textarea.form-textarea,
.form-disabled select.form-select
shoulb be replaced by
.form-disabled .form-text,
.form-disabled .form-tel,
.form-disabled .form-email,
.form-disabled .form-url,
.form-disabled .form-search,
.form-disabled .form-number,
.form-disabled .form-color,
.form-disabled .form-file,
.form-disabled .form-textarea,
.form-disabled .form-select
#edit-cancel : should be replaced by class in the HTML so that a class could be used here.
We can discuss it a little and I can then try to work on a patch for the file.
Comment #4
LewisNymanI think all the general form stuff should stay in form.css, there's loads of stuff that belongs elsewhere though:
File should go in it's own file, but where is this used?
There is a lot of overlap here with generic classes. Let's figure out where all these classes are coming from
Let's move the password related stuff to it's own file
Move this to it's own file, also what is this for?
What is this? We should move it to it's own file... once we figure out what it's for
Here are the results from csslint:
Comment #5
mortendk CreditAttribution: mortendk commentedin the process of banana concensus ive seen a lot of js dependencies in the form, wonder if we wanna fix that issue here or that should be a seperate issue. What it would result in was a massive overhall of all the js dependency classes or rewrite them call to data-attributes selectors, that might grow this to become a mega patch
Comment #6
LewisNymanThere should be no js- selectors in this CSS file, so I think we can move it into a separate issue.
Comment #7
joaogarin CreditAttribution: joaogarin commentedI am trying to find where edit-cancel is being used.. I cant find anything. not from core anyway.
Comment #8
joaogarin CreditAttribution: joaogarin commentedRegarding number 2 :
My biggest concern here would be the tips. I found this basically applies to the input filter tips when switching between filters in edit content or blocks.
My suggestion would be something like :
But I would like to still be sure if it only applies to the filter guidelines or if we keep it more general and just leave ".tips"
".description" also looks a bit too general but I guess this is already a well know class for descriptions (but mostly inside form-item elements)
Comment #9
joaogarin CreditAttribution: joaogarin commentedHello,
I have made some adjustments to the file. I separated it into form.css, password.css and cancel-button.css .
There is still an issue with the @-moz-document, I don't know where this is being used and could quite find out if we still need it.
Maybe some more eyes can make some other things more clear so I can work a bit more on it.
Comment #10
joaogarin CreditAttribution: joaogarin as a volunteer commentedFixed some issues, namely missing spaces at the end of the files.
Comment #11
joaogarin CreditAttribution: joaogarin as a volunteer commentedUpdating issues status to needs review.
I couldnt find what the following is for , I will keep searching on these missing things I don't know where are used so we can figure out if they are indeed needed.
Comment #12
joaogarin CreditAttribution: joaogarin commentedComment #13
joaogarin CreditAttribution: joaogarin as a volunteer commentedBy the way I searched core folder entirely for edit-cancel Id and found nothing.
The same for the two exceptions at the end of form.css file diff-inline-form id and filter-options class.
Maybe someone else might know more about what these are and where they are used, if they are.
Comment #14
joaogarin CreditAttribution: joaogarin as a volunteer commentedJust some screens of some of the forms. More testing required though
Comment #15
LewisNymanNow that the cancel links are styled as buttons, we no longer need this CSS. We can delete this file! Yay
This comment requires a full stop.
I actually think this was fine before when it just said "Form elements." We don't need the word "form " in there
This is changing the design, I don't think we should do this here.
Can we call this file "password-suggestions" to match the class?
I tried removing this CSS and it doesn't seem to do anything. I think it was overriding the old styling.Can we try removing this?
Comment #16
Manjit.Singhremoving
password.css
file andcancel-button.css
Comment #17
LewisNymanNice, now we just need to show we aren't causing any regressions.
Comment #18
Manjit.Singhadding novice tag,
Please take a screenshots of forms of seven theme ;)
Comment #19
manmohandream CreditAttribution: manmohandream at Srijan | A Material+ Company commentedHi Manjit,
I am attaching some screenshots here. Let me know if this works or we need any specific forms screenshots.
Comment #20
Manjit.SinghPlease Upload RTL screenshots as well :)
Comment #21
rudraram CreditAttribution: rudraram at Axelerant commentedAttaching RTL screenshots
Add Node rtl:
Add Menu rtl:
Add Menu Link rtl:
Install new theme rtl:
Comment #22
LewisNymanI found a few more errors being reported by CSSlint:
Comment #23
deepak manhas CreditAttribution: deepak manhas commentedchanges as suggested in #22 by lewis.
Comment #24
Manjit.SinghComment #25
LewisNymanI discussed this with manjit on IRC, it looks like we have to include it twice when we define multiple backgrounds, we should undo this change and we'll just have to put up with the csslint error for now.
Do these classes exist in the markup? Can we get screenshots to show that it still works?
Also I think these classes should be moved into their own files. We should use form.css for generic form styling only
Comment #26
LewisNymanThis patch needed a reroll and it was tricky so re-implemented the patch by hand. I found quite a lot of styling to move around. Seven had a lot of mobile only CSS that was overridding module CSS. In those situations I just added a desktop only media query to the original CSS.
Comment #27
joaogarin CreditAttribution: joaogarin as a volunteer commentedI cant really apply the patch. I think some structure of the folder has changed :
error: core/modules/user/css/user.theme.css: No such file or directory
error: patch failed: core/themes/seven/seven.libraries.yml:28
error: core/themes/seven/seven.libraries.yml: patch does not apply
but regarding the css it looks like this would fixed the issue here : https://www.drupal.org/node/2614198
Comment #36
andypostpatch no longer applies
Comment #37
srilakshmier CreditAttribution: srilakshmier at Valuebound for Valuebound commentedRerolled patch #26 to 9.4.x-dev.
Thank you
Comment #38
ankithashettyTried to fix custom command failure errors in #37 patch, thanks!
Comment #39
andypoststill does not pass
Comment #40
srilakshmier CreditAttribution: srilakshmier at Valuebound for Valuebound commentedTried to fix the custom command failure in #38.
Thanks
Comment #42
longwaveThe Seven theme has been removed from Drupal 10 core. I confirmed that this issue only affects Seven and no other themes included with Drupal core, so I am moving this to the contributed Seven project.