List group item hover issue

[XhmikosR]

Prerequisites

• I have searched for duplicate or closed issues
• I have validated any HTML to avoid common problems
• I have read the contributing guidelines

Describe the issue

Hovering over a list item seems to lose color. Not sure if it's intentional.

Reduced test cases

• https://getbootstrap.com/docs/5.1/components/list-group/#links-and-buttons (works)
• https://twbs-bootstrap.netlify.app/docs/5.1/components/list-group/#links-and-buttons (doesn't work)

What operating system(s) are you seeing the problem on?

Windows

What browser(s) are you seeing the problem on?

Firefox

What version of Bootstrap are you using?

main

[gdibble]

Also noticing this on macOS Monterey 12.1 in Safari, Chrome and Firefox

[gdibble]

I'm running this locally and getting the same outcome as on the netlify deployment. Trying to get a build locally to match the getbootstrap output. I find the cascading order (and thus the line-number differences interesting and quite telling.

@XhmikosR, if I do not submit a PR before you then please let me know what I can do if anything at all to assist. 👍

Note that my working code via npm run docs-serve produce the same cascading order and line-numbers as those on the getbootstrap site, however my hover effect matches that on netlify.

[gdibble]

Cascading order in /scss/_list-group.scss looks correct.
Is it possible that the main site deployment is out of date with Anton's fix?

Ah! @XhmikosR was right about v5.2. Fixed in https://github.com/twbs/bootstrap/pull/35759/files#diff-5acbd4a53dcb8f76abf2cef498ae5a8c5d173ff48ae537c825afa5739a5b5bf0R85

[gdibble]

btw ty @WinterSilence 🙌

[WinterSilence]

@gdibble yes, my fix can be not complete, sometimes it's happening :) p.s. what's is "btw ty"?

[gdibble]

@gdibble yes, my fix can be not complete, sometimes it's happening :) p.s. what's is "btw ty"?

@WinterSilence I understand ☺️ Just wanted to help a bit; hope that's okay

[btw] By The Way, meaning "also..."
[ty] Thank You

[mdo]

Caused by #35869, which I'm reverting. To fix the original issue mentioned in that PR, change the order of the custom CSS classes.

[gdibble]

Thanks @mdo, you rock 🙌