langsys-js-typescript 0.6.0 → 0.6.1

package/CHANGELOG.md

@@ -1,4 +1,12 @@
-## 0.6.0 - unreleased
+## 0.6.1 - 2026-08-15
+
+### Fixed
+
+- **`data-langsys-phrase="false"` / `="0"` are now honored as opt-outs.** 0.6.0 taught the tokenizer to skip subtrees carrying `langsys-php`'s keep-together marker, but matched on attribute presence alone. PHP's `hasPhraseAttribute()` treats presence as intent *while letting an explicit off value opt out* — so we skipped subtrees the author had deliberately un-marked, leaving that content translated by neither SDK. Matching is now value-aware and case-insensitive, mirroring PHP exactly.
+
+  Found by reading `HtmlParser.php` rather than trusting a summary of it — the same second-hand-documentation error this class of bug keeps producing.
+
+## 0.6.0 - 2026-08-15
 
 ### Fixed
 

package/dist/index.d.mts

@@ -628,7 +628,15 @@ interface iContentBlock {
  * additive — `data-langsys-phrase` never appears in DOM our components emit.
  */
 declare const PHRASE_MARKER_ATTRS: readonly ["data-ls-phrase", "data-langsys-phrase"];
-/** True when an element is marked as a self-managed phrase by either SDK. */
+/**
+ * True when an element is marked as a self-managed phrase by either SDK.
+ *
+ * Presence alone means intent, like any boolean HTML attribute — but an
+ * explicit `="false"` or `="0"` opts OUT, matching `langsys-php`'s
+ * `hasPhraseAttribute()` exactly. Without the opt-out we would skip a subtree
+ * the author had deliberately un-marked, and it would then be translated by
+ * neither SDK.
+ */
 declare function isPhraseMarked(element: Element): boolean;
 /**
  * Compute the deterministic content-block id from a `(category, tokens)` pair.

package/dist/index.d.ts

@@ -628,7 +628,15 @@ interface iContentBlock {
  * additive — `data-langsys-phrase` never appears in DOM our components emit.
  */
 declare const PHRASE_MARKER_ATTRS: readonly ["data-ls-phrase", "data-langsys-phrase"];
-/** True when an element is marked as a self-managed phrase by either SDK. */
+/**
+ * True when an element is marked as a self-managed phrase by either SDK.
+ *
+ * Presence alone means intent, like any boolean HTML attribute — but an
+ * explicit `="false"` or `="0"` opts OUT, matching `langsys-php`'s
+ * `hasPhraseAttribute()` exactly. Without the opt-out we would skip a subtree
+ * the author had deliberately un-marked, and it would then be translated by
+ * neither SDK.
+ */
 declare function isPhraseMarked(element: Element): boolean;
 /**
  * Compute the deterministic content-block id from a `(category, tokens)` pair.

package/dist/index.js

@@ -1087,7 +1087,11 @@ var TRANSLATABLE_ATTRIBUTES = [
 ];
 var PHRASE_MARKER_ATTRS = ["data-ls-phrase", "data-langsys-phrase"];
 function isPhraseMarked(element) {
-  return PHRASE_MARKER_ATTRS.some((attr) => element.hasAttribute(attr));
+  return PHRASE_MARKER_ATTRS.some((attr) => {
+    if (!element.hasAttribute(attr)) return false;
+    const value = (element.getAttribute(attr) ?? "").toLowerCase();
+    return value !== "false" && value !== "0";
+  });
 }
 var VALUE_TRANSLATABLE_ELEMENTS = ["button"];
 var VALUE_TRANSLATABLE_INPUT_TYPES = ["submit", "button"];