-
Notifications
You must be signed in to change notification settings - Fork 37
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
GH-84 - Modernize CSS #87
Conversation
feat: (WIP) modernize CSS
For the menu widgets, we didn't implement the up/down arrow keys for moving about the options. Do you think we should do that? |
@jhung could you please clean up the Package dependencies it seems that some could be removed, and maybe update the rest to the latest versions. At least the following could probably be removed:
|
There doesn't appear to be any hover focus for the site. Should we add some for the interactive elements? |
Let's file a new issue for that and implement in the future if it's needed. |
} | ||
|
||
.breadcrumbs li + li::before { | ||
content: ">"; |
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.
Do you think it's necessary to set a specific font to display this character in?
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.
Are you thinking we need to do this because of rendering issues? Would using the unicode be safer?
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.
Depending on the font that is applied to that element, the character may look different. Possibly not there at all if it doesn't exist in the font, although that's probably not an issue with the fonts we'd choose.
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'm thinking perhaps we should use an SVG to avoid this issue altogether. Thoughts?
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.
That's an option. Although it'll have to be added in the markup instead of CSS, if you want to make it easily themeable.
I have filed a feature request to add a no-invert style to child containers (https://issues.fluidproject.org/browse/FLUID-6693). In the meantime, the fl-inverted-color is being overridden for the menu. |
@jobara this is ready for another review. If aren't any outstanding issues, I'm going to prepare to send out an email to get some feedback. |
@jhung I think you can ask for feedback now. I believe the only remaining item from my review is the attribution for the icons. |
@jobara -This is an interesting quirk with UIO - See: https://issues.fluidproject.org/projects/FLUID/issues/FLUID-6696 |
I think if you want to go a route other than https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/hidden Although interestingly it seems that setting the |
package.json
Outdated
@@ -48,11 +46,7 @@ | |||
"postcss": "^8.3.6", |
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.
Could you pin this to a specific version?
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.
What version should be used?
Co-authored-by: Justin Obara <[email protected]>
Modernizing CSS of the Design Guide site. This PR addresses the following issues: