A CSS triangle vanished, because one selector matched by substring
Our stylesheet contains this: [ class *= 'bg-card' ] { border : none !important ; border-width : 0 !important ; } Cards are borderless by design, and this one rule replaced four overlapping copies that all did the same thing in different places. It is deliberate, it is documented, and the substring match is genuinely necessary: Tailwind writes opacity modifiers into the class name itself, so…
The CSS triangle vanished from a balance puzzle because one selector matched the bg-card utility by substring. The stylesheet contained a rule targeting classes containing "border-t" and removing their top border. However, this rule also matched classes like "border-teal-500", "border-t-24", and even a CSS triangle that consisted solely of borders.
The substring match was necessary because Tailwind writes opacity modifiers into class names, so "bg-card/90" needed to be caught. The comment above the rule warned that a border utility on a Card would be silently dead. The triangle's disappearance went unnoticed as tests passed and the class typechecked, only revealing itself upon inspection of the pixels on screen.
The fix involved using an exact selector to target the specific class, rather than relying on a substring match.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
