Skip to content
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

Merged
merged 29 commits into from
Nov 17, 2021
Merged

GH-84 - Modernize CSS #87

merged 29 commits into from
Nov 17, 2021

Conversation

@jhung jhung added the enhancement New feature or request label Oct 15, 2021
@jhung jhung requested a review from jobara October 15, 2021 16:13
@jhung jhung self-assigned this Oct 15, 2021
@jhung jhung marked this pull request as draft October 15, 2021 17:22
@jobara
Copy link
Member

jobara commented Oct 18, 2021

They skip link in mobile is unreadable as it overlaps the UIO button.

Screen Shot 2021-10-18 at 8 00 01 AM

@jobara
Copy link
Member

jobara commented Oct 18, 2021

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?

@jobara
Copy link
Member

jobara commented Oct 18, 2021

@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:

  • sass
  • sass-loader
  • stylus
  • stylus-loader
  • docs-core
  • jQuery-ui

@jobara
Copy link
Member

jobara commented Oct 18, 2021

The contrast themes could use some work. There isn't much visual distinction between the header, navigation, content and footer.

Also the edit on GitHub link and the menu widget options don't have proper focus styling. There isn't any hover styling in the contrast themes either.
Screen Shot 2021-10-18 at 8 17 10 AM

@jobara
Copy link
Member

jobara commented Oct 18, 2021

There doesn't appear to be any hover focus for the site. Should we add some for the interactive elements?

@jhung
Copy link
Member Author

jhung commented Oct 19, 2021

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?

Let's file a new issue for that and implement in the future if it's needed.

src/assets/styles/app.css Outdated Show resolved Hide resolved
src/assets/styles/app.css Outdated Show resolved Hide resolved
}

.breadcrumbs li + li::before {
content: ">";
Copy link
Member

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?

Copy link
Member Author

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?

Copy link
Member

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.

Copy link
Member Author

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?

Copy link
Member

@jobara jobara Nov 1, 2021

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.

src/assets/styles/app.css Outdated Show resolved Hide resolved
@jobara
Copy link
Member

jobara commented Oct 20, 2021

The active menu background colour doesn't appear when the contrast themes are applied.

IMG_5492

@jobara
Copy link
Member

jobara commented Oct 20, 2021

The language menu looks out of place, it might be better if it was lined up with the UIO tab. It might also be nice if these both lined up with the left border of the other content.
Screen Shot 2021-10-20 at 3 55 50 PM

@jhung
Copy link
Member Author

jhung commented Oct 22, 2021

The active menu background colour doesn't appear when the contrast themes are applied.

IMG_5492

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.

@jhung
Copy link
Member Author

jhung commented Oct 26, 2021

@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.

@jobara jobara changed the title Gh 84 - Modernize CSS GH-84 - Modernize CSS Oct 26, 2021
@jobara
Copy link
Member

jobara commented Oct 26, 2021

@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
Copy link
Member

jobara commented Nov 1, 2021

Any empty white box appears on the home page when the Table of Contents is off.
Screen Shot 2021-11-01 at 7 58 34 AM

@jhung
Copy link
Member Author

jhung commented Nov 1, 2021

Any empty white box appears on the home page when the Table of Contents is off. Screen Shot 2021-11-01 at 7 58 34 AM

@jobara -This is an interesting quirk with UIO - display: none is only applied to flc-toc-tocContainer after the Table of Contents has been toggled at least once. display: none, or ideally aria-hidden=true, should be on the container by default and toggled accordingly by UIO.

See: https://issues.fluidproject.org/projects/FLUID/issues/FLUID-6696

@jobara
Copy link
Member

jobara commented Nov 2, 2021

I think if you want to go a route other than display: none it would be to use the hidden attribute. It also means hide for everyone.

https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/hidden

Although interestingly it seems that setting the display style can override the hidden attribute. Not sure if that is only for inline styles or any setting of display.

package.json Outdated
@@ -48,11 +46,7 @@
"postcss": "^8.3.6",
Copy link
Member

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?

Copy link
Member Author

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?

@jobara
Copy link
Member

jobara commented Nov 8, 2021

The focus styling for some elements such as the category links, footer, UIO tab, and links could be improved. In particular some don't provided theme specific contrast styles, and the links in the content are hard to see focus styling for.

Screen Shot 2021-11-08 at 3 59 04 PM

Screen Shot 2021-11-08 at 3 59 14 PM

Screen Shot 2021-11-08 at 3 59 32 PM

Screen Shot 2021-11-08 at 3 59 45 PM

@jobara
Copy link
Member

jobara commented Nov 10, 2021

Focus styling for breadcrumbs could be improved. At the moment it just appears to remove the underline. This is both with and without the contrast themes.

Screen Shot 2021-11-10 at 1 52 41 PM

@jobara
Copy link
Member

jobara commented Nov 10, 2021

Focus styling for the UIO tab does not match theme.

Screen Shot 2021-11-10 at 1 55 07 PM

src/assets/scripts/app.js Outdated Show resolved Hide resolved
@jhung jhung merged commit 3966e12 into inclusive-design:main Nov 17, 2021
@jhung jhung deleted the gh-84 branch November 17, 2021 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants