Problem/Motivation
Split from #2880237: [meta] Refactor system/base library.
This class/CSS was added in 2014 as part of a Seven tabs redesign. It is only used for Claro local tasks, but the CSS is loaded on every request to every Drupal site.
We can move the CSS to its own library, then attach it from the Claro vertical tabs template.
Steps to reproduce
Install standard.
Go to a page like admin/structure/types/manage/article/fields
Resize the browser down to a narrow viewport so you get Claro's hamburger menu for the local tasks.
Make sure the hamburger menu doesn't have unexpected outline button theming - the reset-appearance CSS/class is what removes that.
Proposed resolution
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #23 | 3512404-nr-bot.txt | 91 bytes | needs-review-queue-bot |
| #19 | 3512404-nr-bot.txt | 91 bytes | needs-review-queue-bot |
| #8 | 3512404-nr-bot.txt | 91 bytes | needs-review-queue-bot |
Issue fork drupal-3512404
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3512404-move-reset-appearance.module.css
changes, plain diff MR !11447
Comments
Comment #3
catchComment #4
catchComment #5
smustgrave commentedhaven't manually test but all tests appear to be failing.
Comment #6
catchRebased again.
Comment #7
smustgrave commentedFollowing the steps in the issue summary confirmed everything is behaving as normally.
Comment #8
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #10
dcam commentedIt didn't really need a rebase. Not sure why it thought the MR didn't apply.
Comment #11
nod_can't apply as a patch or rebase the MR from the UI, need some manual rebase/merge
Comment #12
catchRebased again.
Comment #13
dcam commented@catch Sorry I hadn't finished the rebase yet. I was busy with work.
Comment #14
catchAhh apologies from me too, I missed that you were already doing the rebase (although I think I ended up rebasing on top of your in-progress rebase).
These are one of few types of MRs I don't mind rebasing because it's nearly always because the numbers are going down :)
Comment #15
longwaveIs this really useful anywhere else? Can we just deprecate it and add the relevant parts directly to Claro's CSS for
.tabs__trigger?Comment #16
catch@longwave we can't deprecate a files only a library, so that could happen in a follow-up, but not really here, unless we remove it without deprecation.
Comment #17
longwaveBy moving it to its own library anyone who was using it has to make changes by attaching that library, right?
So if they have to make changes anyway maybe we just remove it instead, because this feels kinda useless on its own.
Comment #18
catch#17 that's pretty accurate. If we remove it outright, we'd need to do the following:
1. Copy the CSS to somewhere in stable9 that's always loaded. stable9 doesn't have a catch-all file, only overrides, so either need to pick an existing file that's not a perfect match or add a legacy.css or something.
2. Add the CSS to Claro's tabs CSS somewhere.
Comment #19
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #20
dcam commentedI'm not sure why it thought the MR no longer applies. It was fine. Restoring RTBC.
Comment #21
dcam commentedIt actually needed a rebase today. But now the tests are failing due to deprecations with the following warning...Sorry, I messed up the rebase. I'm trying to fix it.
Comment #22
dcam commentedI restored the original changes from the MR properly. Sorry about that everyone.
Comment #23
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #24
dcam commentedIt didn't actually need a rebase, but I did one anyway just to be certain. Restoring RTBC.
Comment #25
dcam commentedSince one of the other library split issues got committed this one needed a rebase with updated performance metrics. I also updated the deprecation version, but I'm not going to roll back the RTBC status for that, especially since @alexpott allowed self-RTBCing in the other issue for the same minor update.
This issue can be added to the CR I made yesterday for the 11.3.0 splits: #3530832: system/base split into more conditionally loaded libraries.
Comment #28
nod_Committed f38f5f4 and pushed to 11.x. Thanks!
updated the CR too, thanks!
Comment #29
nod_