Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Generic link hover color overrides My Account header component color

クローズ
  • 何か問題がありますか？
#4,642 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@HardeepAsrani がすでに取り組んでいます。

2026年9月30日 から。

評価

この issue はまだ評価されていません。

説明

bug-report bug-report-triage customer report regression

Summary

The My Account header component does not retain its configured hover color after the recent Neve update. The component is expected to use its --hovercolor value while hovered, but the inspected CSS cascade applies Neve's secondary accent instead. This prevents the Header Booster color control from determining the visible hover state and has led to a child-theme !important workaround.

Customer context

Product / area: Neve with Neve Pro Header Booster, My Account header component
Version: Exact installed versions were not provided; the relevant Neve change first shipped in 4.2.13 and remains in 4.2.14
Environment: WordPress frontend with a child theme
Integration / third party: Neve Pro Addon
Reported error / symptom: My Account hover color resolves to the Neve secondary accent rather than the component hover color
Impact: Configured component styling is not reflected without a CSS specificity workaround

Reproduction notes

  1. Use Neve 4.2.13 or 4.2.14 with Neve Pro Header Booster enabled.
  2. Add the My Account component to a header and configure a hover color distinct from Neve's secondary accent.
  3. Hover the .my-account-wrapper link or focus it with the keyboard.
  4. Observe that the computed color comes from the generic Neve link-state rule rather than the component's configured hover value.

The customer supplied the conflicting selectors and reported that an !important child-theme override restores the desired state. A clean local runtime reproduction was not performed.

Diagnosis

Conclusion

This is a confirmed CSS-specificity regression. Neve 4.2.13 changed the generic hover/focus color selector from a:hover / a:focus to a:not([class*="button"]):hover / :focus. The resulting selector has greater specificity than .my-account-wrapper:hover, so the global secondary-accent color wins even though the component defines its own hover color. Commit 17a3c2e0da2446dd162acc4459ada710bbb91ed2 introduced the selector; tag comparison shows the old behavior in 4.2.12 and the conflicting behavior in 4.2.13. No later typography change exists through 4.2.14.

Where this likely occurs
  • User-visible surface: Neve Pro Header Booster's My Account component on hover and focus.
  • assets/scss/components/main/_typography.scss — global anchor state rules, approx. lines 52–60, selector a:not([class*="button"]): assigns --nv-secondary-accent with specificity above the component rule.
  • Neve Pro companion includes/modules/header_footer_grid/assets/scss/new/_my-account.scss — My Account state styling, lines 1–15, selector .my-account-wrapper:hover: assigns the configured --hovercolor but loses the cascade.
  • Neve Pro companion includes/modules/header_footer_grid/assets/scss/style.scss — header asset aggregation, lines 1–9, imports the My Account stylesheet into the bundle documented as included by Blog Pro.
  • Git history: commit 17a3c2e0d is contained in release tags 4.2.13 and 4.2.14; release 4.2.12 retains the lower-specificity generic anchor selector.
Engineering notes

The affected anchor has the class my-account-wrapper, which does not contain button, so it is inside the new global selector's scope. The inspected conflict is deterministic from the emitted selectors: the global rule has specificity (0,2,1), while the component hover rule has (0,2,0). The Pro component uses currentColor for its SVG, so the visible icon follows the overridden anchor color. This entry is routed to Neve because the regression-producing selector and release change are in the theme; the intended component state is defined in the Pro companion.

Test coverage status

The Pro suites e2e-tests/specs/a11y/my-account.spec.ts and e2e-tests/specs/woobooster/header-component.spec.ts exercise My Account markup, accessibility, icon sizing, and dropdown behavior. Neither suite checks computed hover or focus color. No relevant color-state coverage was found during inspection.

What to verify or explore next
  • Reproduce with Neve 4.2.14 and Neve Pro 3.2.12 by assigning distinct secondary-accent and My Account hover colors, then inspect computed color during hover and keyboard focus.
  • Compare the same setup under Neve 4.2.12 and 4.2.13 to validate the identified release boundary at runtime.
  • Run the Header Booster and accessibility Playwright suites after exercising the computed hover/focus color path.
Unknowns / follow-up

The customer's exact Neve and Neve Pro versions were not stated. Runtime reproduction was not performed, but the reported selectors and deterministic cascade match the inspected released source.

Confidence

Confidence: 98/100

Repository inspection confirms that Neve 4.2.13 increased the generic link-state selector's specificity above both affected header-component selectors, and the regression remains in 4.2.14. No matching open GitHub issue was found for either independently testable symptom.

Source: HelpScout #3466631245
Generated by bug-report-triage (ID: bug-report-triage_6abbeeb198c984.22566267)

主要言語
PHP
スター
307
フォーク
89
平均マージ
2日 13時間
マージ済み PR（30日）
23

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Codeinwp/neve のほかの issue

Codeinwp/neve の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。