-
Notifications
You must be signed in to change notification settings - Fork 106
fix(accordion): fixing font-family styling, fixed height demo #2427
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@patternfly/elements": patch | ||
| --- | ||
|
|
||
| `<pf-accordion>`: fixed font family |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is actually incorrect?
https://www.patternfly.org/v4/components/accordion/ shows:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Taken from #2397, we're not sending out a RedHatTextUpdated from the issue itself so we would need to update this to Red Hat Text.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but accordion needs to match up with pf styles. better to load the updated font on our site rather than diverge, IMO
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see this both ways. In the past, we have said "if we can do better than the pfv4 components...", So I think you could definitely make the argument that this is one of those cases
On the other hand, the source material clearly specifies the "updated" font face. It seems hard to justify making this change just for our docs site, when we could just load that font on the site. Pfe is supposed to be visually agnostic to upstream design choices, so long as it doesn't affect accessibility
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@markcaron thoughts? I agree with what Benny is saying here that pfe should be functionally the same as pf w/r/t styling but wanted to see your thoughts on updating it to RedHatText vs keeping it as RedHatTextUpdated?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brianferry @bennypowers, can we not add both to the font stack? That will keep the parity with PFv4's font ("RedHatTextUpdated") as well as work within our site which uses the more universally accepted "Red Hat Text".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but why diverge from patternfly at all? that's why we have the RHDS font tokens
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can, but PatternFly doesn't, so we shouldn't. PFE is not supposed to have opinions on things like font stacks, and I don't want to maintain a "tweaks file" which specifies where and how PFE diverges from PatternFly design specs. If we want to change this in the font stack, we have to make a PR to PF core.