Making WordPress.org

Opened 7 weeks ago

Closed 6 weeks ago

#8178 closed defect (bug) (fixed)

Button primary text color inconsistent on first load vs visited state.

Reported by: bhavin2312's profile bhavin2312 Owned by:
Milestone: Priority: normal
Component: Make (Get Involved) / P2 Keywords: needs-testing needs-patch
Cc:

Description

On make.wordpress.org/chat/ the primary button text color
is not white on initial page load.

After refreshing or after the link becomes :visited,
the text color changes to white.

This appears to be caused by styling applied only to
.button-primary:visited instead of the default link state.

Suggested fix:
Ensure .button-primary and .button-primary:visited
both explicitly define color: #fff;

This will make the button color consistent on first load.

Thank you.

Attachments (1)

Bhavin Gohel (@bhavin2312) – WordPress user profile _ WordPress.org.webm (1.9 MB) - added by bhavin2312 7 weeks ago.

Download all attachments as: .zip

Change History (8)

#1 @nimeshatxecurify
7 weeks ago

  • Component changed from WordPress.org Site to Make (Get Involved) / P2

Can confirm this behavior!

This ticket was mentioned in Slack in #meta by nimeshatxecurify. View the logs.


7 weeks ago

#3 @rahultank
6 weeks ago

Tested Meta ticket #8178 live on make.wordpress.org/chat/ (March 2026).

Bug reproduction:

  1. Opened https://make.wordpress.org/chat/ in a fresh browser session (no cached visited state)
  2. Observed primary button text color — appears non-white on first load
  3. After refreshing or after the link registers as :visited, the color becomes white (#fff)

Root cause (confirmed by CSS inspection):
The .button-primary:visited rule defines color: #fff but the base .button-primary selector does not explicitly set color. This means the browser's default link color bleeds through on first load before the :visited state is applied.

Found 0 CSS rules matching .button-primary:

Suggested fix (from ticket): Add color: #fff to the base .button-primary selector (not just :visited). This is a one-line CSS change with no side effects.

Last edited 6 weeks ago by rahultank (previous) (diff)

#4 @nimeshatxecurify
6 weeks ago

@dd32 Could I get your input on this? Is this something that can be resolved by raising a PR, or does it involve making changes through wp-admin?

Any advice would be greatly appreciated. Thank you!

#5 @dd32
6 weeks ago

@nimeshatxecurify https://make.wordpress.org/chat/ appears to be a site running the TwentyTwelve theme, It appears to use wp4.css (Which is in the repo: https://github.com/WordPress/wordpress.org/tree/trunk/wordpress.org/public_html/style) and Custom CSS via the customizer (Based on the existence of #wp-custom-css in the source of the page).

I would suggest that you can use Chrome Devtools content overrides, and/or in-browser editing tools to find styles that work for the page, which you can suggest here as a comment. I'll review & make the changes as suggested.

#6 @nimeshatxecurify
6 weeks ago

@dd32 Thank you so much for your quick response.

I believe the below targeted custom CSS would address the issue. Let me know your thoughts.

a.button-primary { color: #fff; }

#7 @dd32
6 weeks ago

  • Resolution set to fixed
  • Status changed from new to closed

Thanks, I've updated the relevant CSS, looks like that works.

I've added the Meta Contributor badge to those on this ticket.

Note: See TracTickets for help on using tickets.