Rhythm 2.0 Specifications

Appearance

ATS-PFM-CSH-002Fit the page to the available workspace: Capability Test Specification

Markdown

ATS-PFM-CSH-002

Fit the page to the available workspace: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-CSH-002

Design

Executed by
TST-PFM-CSH-001, TST-PFM-CSH-002, TST-PFM-CSH-010

KindAcceptance test setProduct areaPlatformModuleConsole Shell and NavigationRevision3

Read atreact-console baf6dae3services-platform ad3f6a65rhythm-v2-docs 25e253cb

Fit the page to the available workspace: Capability Test Specification ​

Coverage ​

The coverage map describes specified proof, not a passing run. Each mandatory rule below has a scenario or an explicit finding; a proposed scenario remains an execution obligation even when its expected outcome follows the pinned implementation.

Mandatory RuleScenarios or Finding
BR-CAP-PFM-CSH-002-01ATS-PFM-CSH-002-01
BR-CAP-PFM-CSH-002-03ATS-PFM-CSH-002-02
BR-CAP-PFM-CSH-002-05ATS-PFM-CSH-002-03
BR-CAP-PFM-CSH-002-06ATS-PFM-CSH-002-04, ATS-PFM-CSH-002-06, ATS-PFM-CSH-002-07
BR-CAP-PFM-CSH-002-07ATS-PFM-CSH-002-05

Restoration requires both expanded and already-collapsed arrival fixtures, departure while manually reopened, and independent mobile navigation. Width measurement must also include the docked assistant.

The workspace grows while the column remains centered within its new bounds.

The interaction rows cite the contracts they exercise. Related combinations without a complete case remain in the coverage finding, together with cross-capability workflows and permission boundaries. A helper assertion is bound only for its stated outcome; the full browser handoff remains proposed until a suite checks it.

Pinned source and exact test anchors are recorded in frontmatter. Test bindings record static assertion review and use the executable-suite register; no product test result is inferred from that review. The prior planning and design examinations supply context, while this continuation records the remaining proof obligations explicitly.

Coverage

  • Rule covered
  • Transition gap: FND-PFM-CSH-052
  • Validation gap: FND-PFM-CSH-052
  • Permission gap: FND-PFM-CSH-052
  • Edge gap: FND-PFM-CSH-052
  • Failure gap: FND-PFM-CSH-052
  • Boundary covered
  • Concurrency gap: FND-PFM-CSH-052
  • Invariant gap: FND-PFM-CSH-052
  • Interaction gap: FND-PFM-CSH-052

Test Scenarios

7 scenarios proving CAP-PFM-CSH-002; 5 bound to an existing test.

01 Rendered layouts distinguish full and standard widthinvariantunittest
Proves
BR-CAP-PFM-CSH-002-01
Preconditions
Two layout fixtures use the default and standard width choices.
Steps
Render both fixtures and inspect their outer and inner containers.
Expected
Default width fills the workspace; standard width centers a capped inner column.
Data
Independent fixture inputs for the variants listed in this case.
Bound to
Source
react-console:components/console/__tests__/page-layout.test.tsx#fills the workspace when no width is given
02 Enumerated screens declare the expected page widthruleunittest
Proves
BR-CAP-PFM-CSH-002-03
Preconditions
Source fixtures include the specified configuration lists, Tasks and field editor.
Steps
Inspect each screen’s root layout declaration.
Expected
The enumerated lists select standard width; Tasks and the field editor retain full width.
Data
Independent fixture inputs for the variants listed in this case.
Bound to
Source
react-console:components/console/__tests__/page-layout-adoption.test.ts#configuration lists render at the standard width
03 Leaving the designer restores an expanded arrival statetransitionbrowserproposed
Proves
BR-CAP-PFM-CSH-002-05
Preconditions
Desktop navigation is expanded before the designer opens.
Steps
Open the contact form designer and then leave for the contacts list.
Expected
The designer collapses navigation while open; departure restores expansion.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:docs/page-layouts.md#Pages that collapse the sidebar
04 Folding adds usable space and retains centeringboundarybrowsertest
Proves
BR-CAP-PFM-CSH-002-06
Preconditions
Standard and full-width pages are opened at a 1,920-pixel viewport.
Steps
Use the button fold cases and the separate keyboard fold case; measure the remaining workspace.
Expected
The standard page stays centered and full-width content fills the enlarged workspace.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Bound to
Source
react-console:e2e/layout/page-layouts.spec.ts#contact types stays standard and centred
05 A fresh load ignores the preceding fold choicetransitionbrowserproposed
Proves
BR-CAP-PFM-CSH-002-07
Preconditions
The sidebar was collapsed and its cookie was written.
Steps
Reload the console after changing the fold choice.
Expected
The desktop sidebar starts expanded; record the previous cookie without treating it as a restored preference.
Data
A fresh browser context, isolated account fixtures and controlled responses for the listed transitions.
Source
rhythm-v2-docs:specs/platform/console-shell/planning/capabilities/CAP-PFM-CSH-002-give-each-page-the-room-it-needs.md
06 Keyboard folding changes the standard page workspaceinteractionbrowsertest
Proves
BR-CAP-PFM-CSH-002-06 BR-CAP-PFM-CSH-003-05
Preconditions
Contact Types is open on a wide desktop.
Steps
Press the sidebar command shortcut and measure the standard column.
Expected
The workspace grows while the column remains centered within its new bounds.
Data
A fresh browser context, isolated account fixtures and controlled responses for the listed transitions.
Bound to
Source
react-console:e2e/layout/page-layouts.spec.ts#the keyboard shortcut collapses it too
07 Docking the assistant preserves both page-width calculationsboundarybrowsertest
Proves
BR-CAP-PFM-CSH-002-06
Preconditions
Standard and full pages are available at the enumerated wide viewports.
Steps
Dock Jazz beside each page and measure against the remaining content workspace.
Expected
The standard column is centered and capped; every full page spans the narrower workspace.
Data
The pinned route and page fixtures; browser measurements use a fresh demonstration context at each tested viewport.
Bound to
Source
react-console:e2e/layout/page-layouts.spec.ts#Jazz AI docked

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software