-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: WP-197 use @layer's / help migrate Frontera #856
Merged
wesleyboar
merged 14 commits into
main
from
feat/WP-197-use-css-layers-to-help-migrate-frontera
Oct 1, 2024
Merged
feat: WP-197 use @layer's / help migrate Frontera #856
wesleyboar
merged 14 commits into
main
from
feat/WP-197-use-css-layers-to-help-migrate-frontera
Oct 1, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Frontera migration — TACC/Core-CMS-Custom#293 — uses @layers, but then Frontera styles yield to Core-CMS styles. They yield to Core-CMS because Core-CMS — with `TACC_CORE_STYLES_VERSION=0` — has all its styles in an anonymous layer. (CSS in an anonymous layer beats CSS in a named layer.)
wesleyboar
force-pushed
the
feat/WP-197-use-css-layers-to-help-migrate-frontera
branch
from
July 25, 2024 19:32
865cd70
to
ebe86e4
Compare
19 tasks
wesleyboar
changed the title
feat: WP-197 use @layer's / help migrate Frontera
feat: WP-197 use @layer's / help migrate Frontera ⚠️
Sep 20, 2024
wesleyboar
changed the title
feat: WP-197 use @layer's / help migrate Frontera ⚠️
feat: WP-197 use @layer's / help migrate Frontera
Sep 20, 2024
So, change `project` to `project.core`.
Recent CSS fix for header was only applied to v1-origin sites. The fix should be applied to v4.18+ sites.
wesleyboar
deleted the
feat/WP-197-use-css-layers-to-help-migrate-frontera
branch
October 1, 2024 00:03
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Use
@layer
for Core-CMS stylesheets loaded whenTACC_CORE_STYLES_VERSION=0
.Frontera migration — TACC/Core-CMS-Custom#293 — uses @layers, but then Frontera styles yield to Core-CMS styles.
They yield to Core-CMS because Core-CMS — with
TACC_CORE_STYLES_VERSION=0
— has all its styles in an anonymous layer.(CSS in an anonymous layer beats CSS in a named layer.)
Related
Changes
@layer
's@layer
(only to match
TACC_CORE_STYLES_VERSION=2
CMS use of@layer
's)Testing / UI
feat: WP-197 migrate frontera portal Core-CMS-Custom#293
enhance(ecep): ecep_cms → ecep_assets Core-CMS-Custom#321
feat: epoc_assets Core-CMS-Custom#320
Notes
PR Problems That Have Since Been Fixed
#css-booststrap
node cuz it does not exist now.