Comment Form: Submit button does not match theme styles

[chad1008]

Impacted plugin

Jetpack, mu wpcom

Quick summary

When a theme's color styles are set in the Site Editor, the selected color is applied to buttons across the site. On WordPress.com hosted sites, the comment form's Submit button does not render in the displayed color, and instead uses a default blue.

This appears to be specific to WordPress.com, as I wasn't able to reproduce it on a Jurassic Ninja instance. On WordPress.com, the issue did not appear to be theme-specific.

Steps to reproduce

1. On any WordPress.com hosted site, open the site editor, select Colors and choose a palette that makes the buttons appear in a recognizable color. Preferably not blue 😆
2. Create and publish a new post and add a Buttons block with at least one button
3. View your new post, note the color of the button in the post content
4. Scroll down and enter some text in the comment field to enable the Comment button. Note the button color here as well.

A clear and concise description of what you expected to happen.

I expected the comment form button to match the color declared by the theme/style selection (which I think it used to, if I'm not mistaken)

What actually happened

The button on the comment form does not match, and renders in one of our default blues. Which, don't get me wrong, is a lovely blue. Truly stunning. Props to the designers on that blue, truly. It's just... not matchy ya know?

Impact

Most (> 50%)

Available workarounds?

Yes, difficult to implement

Platform (Simple and/or Atomic)

Simple, Atomic

Logs or notes

Reproduced on Twenty Twenty Four and Infield themes.

[filipanoscampos]

The user on 8073990-zd-a8c would like to be updated once the issue is solved.

[github-actions[bot]]

Support References

This comment is automatically generated. Please do not edit it.

• [ ] 8073990-zen
• [ ] 7875379-zen

[hngdny]

Another report on 7875379-zd-a8c Theme: Sten

[github-actions[bot]]

This issue has been marked as stale. This happened because:

• It has been inactive for the past 6 months.
• It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, `[Type] Feature Request`, `[Type] Enhancement`, `[Type] Janitorial`, `Good For Community`, `[Type] Good First Bug`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[wynwin]

📌 REPRODUCTION RESULTS

• Tested on Simple – Replicated
• Tested on Atomic – Replicated

Theme: Sten

📌 ACTIONS

• Triaged
• Characterized as a bug.
• Leaving assigned to Team Vertex, but pinging @Automattic/loop here in case this is something your team can help with.

[davemart-in]

Added to our board. 👍