(causeway) 03/07: docs(openspec): archive tooltip contrast improvement

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

danhaywood pushed a commit to branch htmx
in repository https://gitbox.apache.org/repos/asf/causeway.git

commit cba9be7a94c2842a3612724b73520f2b96157b04
Author: Dan Haywood <da...@haywood-associates.co.uk>
AuthorDate: Sun Aug 30 19:52:19 2026 +0200

    docs(openspec): archive tooltip contrast improvement
---
 .../.openspec.yaml                                 |  0
 .../2026-08-30-improve-tooltip-contrast}/design.md |  0
 .../proposal.md                                    |  0
 .../specs/domain-web-components/spec.md            |  0
 .../2026-08-30-improve-tooltip-contrast}/tasks.md  |  0
 openspec/specs/domain-web-components/spec.md       | 24 ++++++++++++++++++++++
 6 files changed, 24 insertions(+)

diff --git a/openspec/changes/improve-tooltip-contrast/.openspec.yaml b/openspec/changes/archive/2026-08-30-improve-tooltip-contrast/.openspec.yaml
similarity index 100%
rename from openspec/changes/improve-tooltip-contrast/.openspec.yaml
rename to openspec/changes/archive/2026-08-30-improve-tooltip-contrast/.openspec.yaml
diff --git a/openspec/changes/improve-tooltip-contrast/design.md b/openspec/changes/archive/2026-08-30-improve-tooltip-contrast/design.md
similarity index 100%
rename from openspec/changes/improve-tooltip-contrast/design.md
rename to openspec/changes/archive/2026-08-30-improve-tooltip-contrast/design.md
diff --git a/openspec/changes/improve-tooltip-contrast/proposal.md b/openspec/changes/archive/2026-08-30-improve-tooltip-contrast/proposal.md
similarity index 100%
rename from openspec/changes/improve-tooltip-contrast/proposal.md
rename to openspec/changes/archive/2026-08-30-improve-tooltip-contrast/proposal.md
diff --git a/openspec/changes/improve-tooltip-contrast/specs/domain-web-components/spec.md b/openspec/changes/archive/2026-08-30-improve-tooltip-contrast/specs/domain-web-components/spec.md
similarity index 100%
rename from openspec/changes/improve-tooltip-contrast/specs/domain-web-components/spec.md
rename to openspec/changes/archive/2026-08-30-improve-tooltip-contrast/specs/domain-web-components/spec.md
diff --git a/openspec/changes/improve-tooltip-contrast/tasks.md b/openspec/changes/archive/2026-08-30-improve-tooltip-contrast/tasks.md
similarity index 100%
rename from openspec/changes/improve-tooltip-contrast/tasks.md
rename to openspec/changes/archive/2026-08-30-improve-tooltip-contrast/tasks.md
diff --git a/openspec/specs/domain-web-components/spec.md b/openspec/specs/domain-web-components/spec.md
index 961cc86886e..f09abf2215e 100644
--- a/openspec/specs/domain-web-components/spec.md
+++ b/openspec/specs/domain-web-components/spec.md
@@ -1970,3 +1970,27 @@ Nested parameter declarations MUST NOT add, remove, reorder, hide, disable, defa
 - **WHEN** `multi-line` is absent, malformed, non-positive, one, or incompatible with the authoritative input shape
 - **THEN** the parameter retains its established qualified editor
 - **AND** unrelated parameter presentation remains available
+
+### Requirement: Distinct customizable tooltip presentation
+Component-owned action, member, collection, parameter, and disabled-state tooltips SHALL use a shared high-contrast explanatory surface that is visually distinct from adjacent action controls.
+The default treatment MUST use a light neutral background, dark text, a visible boundary, and stable `--causeway-*` customization variables without changing tooltip semantics or activation.
+
+#### Scenario: Tooltip appears beside a filled action
+- **WHEN** pointer or keyboard interaction reveals a tooltip adjacent to a filled action control
+- **THEN** the tooltip uses the light neutral explanatory surface and dark text
+- **AND** its border or elevation distinguishes it from both the page and the action control
+
+#### Scenario: Different component tooltip families render
+- **WHEN** an action description, member description, collection description, action-parameter description, or disabled reason is presented as a tooltip
+- **THEN** each tooltip consumes the same background, text, border, and shadow presentation tokens
+- **AND** existing content, sections, positioning, responsive bounds, pointer access, keyboard access, and accessible associations remain unchanged
+
+#### Scenario: Application customizes tooltip presentation
+- **WHEN** an application overrides the documented tooltip variables
+- **THEN** component-owned tooltip background, text, border, and shadow presentation use those values
+- **AND** no component markup or semantic event customization is required
+
+#### Scenario: Optional theme is absent
+- **WHEN** an application installs only the structural component styles
+- **THEN** equivalent high-contrast light tooltip fallback values remain effective
+- **AND** tooltip content remains readable and visually bounded