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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PM-6100's green universal-navigation footer links are already fixed on current
dev. This PR records the cause, existing fixes, and verified behavior without adding a redundant CSS override.The shared 2026
body.work-app adefault originally recolored footer links. PM-6091 commitcb108c147a(September 9) restored white footer links and retained the CTA's dark text. Opportunities already scopes the theme to its content wrapper, outside the sibling footer.Validation: 18 Chromium checks against the repository's compiled Sass passed at desktop/mobile widths across normal, hover, and focus states and Opportunities → Work → Opportunities body-class changes. Content links remain teal, footer links white, and CTA text dark.
yarn lintand the production build pass (Node 22.13.0, 16 GB Node heap; the default heap was insufficient). The browser check uses an isolated footer fixture, not a live deployment.Ticket: https://topcoder.atlassian.net/browse/PM-6100