feat(card): convert card-content to shadow DOM #30759
Open
+48
−84
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
TODO font size does not work due to global styles
brandyscarney
commented
Dec 18, 2025
Member
Author
There was a problem hiding this comment.
I left this test in so we would still capture how headings look in cards but since we are no longer styling them directly I can remove them if desired.
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.
Issue number: internal
What is the current behavior?
Card content has no encapsulation.
What is the new behavior?
Convert
ion-card-contentto Shadow DOM which improves consistency among components & CSP compatibility.Does this introduce a breaking change?
There should not be any breaking changes related to targeting inner elements since
ion-card-contentdoes not have any internal elements of its own. However, some user styles may break due to the removal of thecard-content-{mode}class or changes in selector specificity. Additionally, the styles targeting heading elements in card-content were removed. Users that wish to have custom styling for headings should add their own CSS targeting them.