plogins-swatch 1.0.19

• New: the chosen value shows beside the attribute label, as in "Colour: Red", so a colour or image swatch also says its name in words. It clears with "Clear" and follows WooCommerce when it restores a default choice, and screen readers announce the change.

Full history: https://plogins.com/plogins-swatch/changelog/

plogins-swatch 1.0.18

• Fixed: out-of-combination swatches were never disabled and the "Clear" link left the old swatches highlighted. WooCommerce fires its variation events through jQuery, which a native event listener never receives, so the swatches missed every update. They now subscribe through WooCommerce's own jQuery.
• Fixed: adding or saving any attribute term stored a black swatch colour, because a colour field always submits a value. A term you never gave a colour then showed a black dot, and a colour attribute could no longer fall back to the dropdown. A "No colour" checkbox now keeps a term without one; picking a colour unticks it. Terms saved black by earlier versions keep that colour until you tick "No colour" on them.

Full history: https://plogins.com/plogins-swatch/changelog/

plogins-swatch 1.0.17

• The upgrade notice's "Coming soon" and "Get notified" labels are English source strings for every language; Polish sites used to get their own Polish source text, which translators in other languages then saw untranslated.

Full history: https://plogins.com/plogins-swatch/changelog/

plogins-swatch 1.0.16

• Display name drops the "Plogins " prefix. The slug, the text domain and every option key are unchanged, so nothing on an existing install moves.

Full history: https://plogins.com/plogins-swatch/changelog/

plogins-swatch 1.0.15

• The sidebar upgrade promo now follows the same dismissal as the banner. Dismissing the banner used to leave a full-height advert on the settings screen for good, which is not what the WordPress.org guideline on upgrade prompts means by used with moderation.

Full history: https://plogins.com/plogins-swatch/changelog/

plogins-swatch 1.0.14

• Security (low): swatch markup is now passed through wp_kses() with an explicit allowlist at the point it is printed. Every renderer escapes the values it writes, but each one ends in a filter, so what actually reached the page was whatever the last callback returned. An add-on, or anything else hooking those filters, could put unescaped markup on a storefront page. The allowlist covers the elements and attributes the swatches use, including img for the paid edition's image swatches and data-* for the values the script reads.
• Note: an inline colour that is not a hex value is dropped by WordPress when the markup is filtered, so a callback returning rgb(...) loses that colour. Colours saved on an attribute term are unaffected: they go through sanitize_hex_color() on the way in and on the way out.

Full history: https://plogins.com/plogins-swatch/changelog/