You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@causeway.apache.org by da...@apache.org on 2026/08/28 04:30:18 UTC
(causeway) 16/16: docs(openspec): archive property tooltip and alignment refinement
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 8dd9e3baf241ade705d737405ed27cf8a8ce812f
Author: Dan Haywood <da...@haywood-associates.co.uk>
AuthorDate: Fri Aug 28 01:12:39 2026 +0200
docs(openspec): archive property tooltip and alignment refinement
---
.../.openspec.yaml | 0
.../design.md | 0
.../proposal.md | 0
.../specs/domain-web-components/spec.md | 0
.../tasks.md | 0
openspec/specs/domain-web-components/spec.md | 12 ++++++++++--
6 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/openspec/changes/refine-property-description-and-value-alignment/.openspec.yaml b/openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/.openspec.yaml
similarity index 100%
rename from openspec/changes/refine-property-description-and-value-alignment/.openspec.yaml
rename to openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/.openspec.yaml
diff --git a/openspec/changes/refine-property-description-and-value-alignment/design.md b/openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/design.md
similarity index 100%
rename from openspec/changes/refine-property-description-and-value-alignment/design.md
rename to openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/design.md
diff --git a/openspec/changes/refine-property-description-and-value-alignment/proposal.md b/openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/proposal.md
similarity index 100%
rename from openspec/changes/refine-property-description-and-value-alignment/proposal.md
rename to openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/proposal.md
diff --git a/openspec/changes/refine-property-description-and-value-alignment/specs/domain-web-components/spec.md b/openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/specs/domain-web-components/spec.md
similarity index 100%
rename from openspec/changes/refine-property-description-and-value-alignment/specs/domain-web-components/spec.md
rename to openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/specs/domain-web-components/spec.md
diff --git a/openspec/changes/refine-property-description-and-value-alignment/tasks.md b/openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/tasks.md
similarity index 100%
rename from openspec/changes/refine-property-description-and-value-alignment/tasks.md
rename to openspec/changes/archive/2026-08-28-refine-property-description-and-value-alignment/tasks.md
diff --git a/openspec/specs/domain-web-components/spec.md b/openspec/specs/domain-web-components/spec.md
index 3d7a5f5f405..4a641384b68 100644
--- a/openspec/specs/domain-web-components/spec.md
+++ b/openspec/specs/domain-web-components/spec.md
@@ -25,11 +25,17 @@ Each domain member component SHALL derive its supported read behavior from the i
### Requirement: Read-only property semantics
The `<causeway-property>` component SHALL render property visibility, usability, description, null state, value, loading state, member-scoped errors, and semantic multiline presentation from its context state and public attributes.
+A standard GraphQL `String` property value MUST be explicitly aligned to the logical start so its view and edit presentations remain consistent.
#### Scenario: Visible property value
- **WHEN** a visible property read completes successfully
- **THEN** the component renders its semantic label and value using the selected value renderer
+#### Scenario: String property value
+- **WHEN** a visible property has the standard GraphQL `String` output type
+- **THEN** the component marks its output with the semantic string-value presentation class
+- **AND** baseline and cohesive-theme presentation align the value to the logical start
+
#### Scenario: Property description is available
- **WHEN** a property descriptor supplies a non-redundant description
- **THEN** the component exposes that description as the property's default explanatory tooltip and accessible description
@@ -50,9 +56,11 @@ The `<causeway-property>` component SHALL render property visibility, usability,
- **THEN** the component omits the property's label, value, and interactive content
#### Scenario: Disabled property
-- **WHEN** the rich object state reports that a property is disabled
+- **WHEN** the rich object state reports that a property is disabled with a bounded reason
- **THEN** the component exposes its disabled state without presenting an edit affordance
-- **AND** exposes the disabled reason through a separate focusable tooltip indicator and accessible description without replacing the property-description tooltip or requiring a key modifier
+- **AND** attaches the disabled-reason tooltip to the property label rather than rendering a separate information indicator
+- **AND** makes the label tooltip available by pointer hover and ordinary keyboard focus
+- **AND** retains the disabled reason as an accessible description without replacing a distinct property-description tooltip
#### Scenario: Null property
- **WHEN** the property value is null