Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
CSS
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Mar 2024 at 21:55 UTC
Updated:
26 May 2025 at 09:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
kentr commentedPossible duplicate of #2880237: [meta] Refactor system/base library, as some work for
tablesorthas already been done in that issue.Comment #3
catchGood point - I think I opened this before I found that one. Closing.
Comment #4
catchActually no. We should split the change out to here since it's tricky.
Comment #6
xamountI've adjusted the tablesort.module.css but I could not figure where is the best place to attach the new library.
Someone please review and guide me here.
Comment #9
catch@xamount this is a tricky one, I ended up opening a new MR because there's been some related changes in core since your branch was open. With attachments, I wasn't sure either but added a template_preprocess implementation which works and is at least compact.
Comment #10
catchComment #11
catchShould be reviewable/testable now.
Comment #12
smustgrave commentedSo the way I tested this one was by just created a few nodes with A,B,C in front of the title. Then on the content view verified the table sorting worked as expected.
If different types of sorting are needed let me know, else believe this is good.
Comment #14
nod_Paths needs to be updated after css file move
Comment #15
catchUpdated the icon paths, good spot, not sure how I missed it in manual testing, maybe claro overrides hid the bug?
Comment #16
nod_Yes I don't think any core theme uses this file
Comment #17
smustgrave commentedFeedback appears to be addressed.
Comment #18
smustgrave commentedOops my mistake.
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
catchRebased.
Comment #21
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 #23
dcam commentedRebased
Comment #26
nod_Committed 4166328 and pushed to 11.x. Thanks!
Comment #27
lauriiiThere's a regression with this change:
Comment #28
nod_Comment #29
catchWorking on it, MR shortly.
Comment #30
catchOK the problem is that when the tablesort CSS is moved to the library, Claro's classy tablesort.css, which specifies a td.is-active background color, is loaded after Claro's tables.css, which specifies background: none;
Adding an MR that just removes the declaration from classy.css - it makes no sense for Claro to define two different CSS rules for the same class, the classy one was just never getting used until the regression.
More generally, Claro has tablesort.css and tables.css, but defines various styles for tablesort inside tables.css. So it would be worth a follow-up to move all of that styling to tablesort.css to avoid unused CSS when regular, unsortable, tables are rendered.
Comment #32
catchOpened #3520057: Clean up Claro tablesort CSS.
Comment #33
nicxvan commentedExplanation is great, fix is simple, there is one test that looks like a random failure I cannot rerun.
If that passes I think this is rtbc.
Comment #34
smustgrave commentedDoubt the change didn’t break the build step
Comment #36
nod_Committed 7dc9bf7 and pushed to 11.x. Thanks!