/* Trigger styling comes from the site's own component (Cwicly, custom block, …). frontend.js adds .wrv-bound to every trigger it wires up, so these cues work regardless of the configured marker class. */ .wrv-bound{cursor:pointer} .wrv-bound.wrv-playing{outline:2px solid currentColor;outline-offset:2px} /* State, mirrored into the markup by frontend.js: data-wrv-state="ready" + data-wrv-audio="" playable data-wrv-state="pending" detected, no audio yet A trigger with NO data-wrv-state attribute is one this script never reached (JS disabled, bundle error, CSP). That case is deliberately left untouched: every rule below keys on the PRESENCE of "pending", never on the absence of an attribute, so a script failure can never blank the site's controls. Nothing here hides anything by default — see the opt-in setting below. */ /* Opt-in: "Ohne Audio ausblenden" in the plugin settings adds .wrv-hide-pending to . A control that is detected but has no recording is then removed for visitors, so a button can never look identical to a working one while doing nothing when clicked. aria-hidden is NOT needed here: frontend.js already removes every trigger from the accessibility tree, and display:none removes it anyway. */ .wrv-hide-pending [data-wrv-state="pending"]{display:none !important}