@pie-players/pie-tool-answer-eliminator 1.0.0-beta.5 → 1.0.0-beta.7

package/README.md

@@ -89,7 +89,7 @@ For a custom layout inside the toolkit. The tool detects choices under the item
 | `visible` | `visible` | `boolean` | `false` | Shows the elimination buttons; the toolbar toggle sets it |
 | `alwaysOn` | `always-on` | `boolean` | `false` | Shows the buttons regardless of `visible`, for a profile-based accommodation |
 | `strategy` | `strategy` | `'strikethrough' \| 'mask'` | `'strikethrough'` | Elimination styling; any other value uses `strikethrough` |
-| `buttonAlignment` | `button-alignment` | `'left' \| 'right' \| 'inline'` | `'right'` | Button placement relative to the choice |
+| `buttonAlignment` | `button-alignment` | `'start' \| 'end' \| 'inline'` | `'inline'` | Toggle placement: `inline` in the flow after the choice, or `start`/`end` beside it, resolved against the choice's own direction so they mirror under right-to-left content. `left` and `right` are aliases of `start` and `end`; any other value is `inline` |
 | `elementStateKeys` | | `Record<string, string>` | `{}` | Composite key `assessmentId:sectionId:attemptId:itemId:elementId` per PIE element, by model id, into the runtime context's element tool state store. A choice is tracked under its nearest ancestor with a listed id and persists under that key; choices outside a listed element are kept in memory only |
 
 ## Global Element ID Format
@@ -263,6 +263,8 @@ For browsers without the Highlight API, each strategy falls back to a class on t
 
 Each choice gets its own elimination toggle button (class `pie-answer-eliminator-toggle`, rendered as `⊗`) appended to its `container`. Clicking the button toggles that choice through the active strategy and calls `setEliminated`. Eliminating is blocked while `isEliminable()` returns false. An active button is marked with `pie-answer-eliminator-toggle--active` and `aria-pressed="true"`; clicking again restores the choice.
 
+The toggle's accessible name ("Toggle elimination for {choice}", with "Unlabeled choice" standing in for a choice without text) and the "(eliminated)" announcement come from the players' catalog under `tools.answerEliminator`, in the interface locale of the runtime context. Both carry that locale's `lang` and `dir` while the choice content keeps its own, and a locale change relabels them in place without dropping eliminations.
+
 ## Cleanup
 
 The ElementToolStateStore provides cleanup methods:

package/custom-elements.json

@@ -43,9 +43,10 @@
 							"kind": "field",
 							"name": "buttonAlignment",
 							"type": {
-								"text": "'left' | 'right' | 'inline'"
+								"text": "'start' | 'end' | 'inline' | 'left' | 'right'"
 							},
-							"default": "'right'",
+							"default": "'inline'",
+							"description": "Toggle placement: `inline` in the flow after the choice, or `start`/`end` beside it, mirrored under right-to-left content; `left` and `right` alias `start` and `end`.",
 							"attribute": "button-alignment"
 						},
 						{
@@ -89,7 +90,8 @@
 							"type": {
 								"text": "string"
 							},
-							"default": "'right'",
+							"default": "'inline'",
+							"description": "Toggle placement: `inline` in the flow after the choice, or `start`/`end` beside it, mirrored under right-to-left content; `left` and `right` alias `start` and `end`.",
 							"fieldName": "buttonAlignment"
 						},
 						{

package/dist/element-props.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Store key per PIE element, by the element's model id (which is also its DOM
+ * id). A choice persists under the key of the nearest ancestor listed here.
+ */
+export type ElementStateKeys = Readonly<Record<string, string>>;
+/** Inputs shared by the component and its native element declaration. */
+export interface AnswerEliminatorProps {
+    visible?: boolean;
+    strategy?: 'strikethrough' | 'mask';
+    alwaysOn?: boolean;
+    buttonAlignment?: 'start' | 'end' | 'inline' | 'left' | 'right';
+    elementStateKeys?: ElementStateKeys;
+}

package/dist/index.d.ts

@@ -1,7 +1,9 @@
-/**
- * pie-tool-answer-eliminator - PIE Assessment Tool
- *
- * Importing this package registers `<pie-tool-answer-eliminator>`. The build
- * entry is the component, so this file is the type entry alone.
- */
-export type {};
+import { AnswerEliminatorProps } from './element-props.js';
+/** Native host interface for `<pie-tool-answer-eliminator>`. Properties may be unset until it mounts. */
+export interface PieToolAnswerEliminatorElement extends HTMLElement, AnswerEliminatorProps {
+}
+declare global {
+    interface HTMLElementTagNameMap {
+        "pie-tool-answer-eliminator": PieToolAnswerEliminatorElement;
+    }
+}