forked from akai/readest
0564b4dd48
In #4230 the new .btn-contrast block was inserted into the middle of the existing rule [data-eink='true'] button, [data-eink='true'] .btn { color: theme('colors.base-content') !important; } which left [data-eink='true'] button grouped with .btn-contrast (applying background-color/border/color: base-100) and orphaned [data-eink='true'] .btn as its own rule. Net effect on any button that also has class="btn" — toolbar icon buttons, popup actions, etc.: [data-eink='true'] button bg=base-content, color=base-100 (specificity 0,1,1) [data-eink='true'] .btn color=base-content (specificity 0,2,0) The .btn rule wins on color, so the button ends up with a base-content background AND base-content text color. react-icons children render with fill: currentColor → invisible icon on solid background → every toolbar/popup button becomes a solid black (light mode) or solid white (dark mode) square in e-ink mode. Fix is the minimal regroup that #4230 was apparently trying to make: put the new .btn-contrast block AFTER the existing eink button/.btn selector list rather than splitting it. Tested locally: in e-ink mode, all annotation toolbar / quick-action popup buttons recover their icon glyphs; .btn-contrast still renders as the intended solid-CTA in both modes.