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

Navcurrent: Make current page's footer link bold #9308

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

EricDunsworth
Copy link
Member

The "wb-navcurr" class changes colour schemes in the mega and secondary menus to visually-emphasize the current page.

This adds a similar effect to footer links via bolding. It wouldn't of been practical to change text/background colours in that context since WET's footer links don't resemble buttons.

The "wb-navcurr" class changes colour schemes in the mega and secondary menus to visually-emphasize the current page.

This adds a similar effect to footer links via bolding. It wouldn't of been practical to change text/background colours in that context since WET's footer links don't resemble buttons.
Copy link
Member

@duboisp duboisp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change in this PR should be merged with your other related navcurrent PR #9307

Prior to apply this change, the style should only be applied when the link exactly match the current page, not an anchor. Like the footer link "About the Web Experience Toolkit" when navigating in the index.en.html page
Also, we will need to identify all the location where we are using that plugin. We need to evaluate the impact of this propose change.

TODO:

  • Merge change with PR Navcurrent: Add aria-current="page" attribute #9307
  • Identify all the instance that use this plugin. In GCWeb and wet-boew
  • Ensure the style is only applied for exact match including the page anchor, not how the wb-navcurr plugin is currently working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants