STV_CR_016: Save the visible view as SVG
Owner request, 2026-10-25 (language-corrected): Add a Save as SVG button that saves the current view, including any opened detailed information, into an SVG file for which the user can choose the location. Owner clarification, 2026-10-25: Export only the currently visible area, rather than the complete expanded graph and all off-screen card content. Source: owner conversation and clarification reply. Baseline: Available local revision
Stakeholder amendment: Save the currently visible ... (STV_SHR_059) requests a per-view Save as SVG control, visible-area capture and reader-selected save location. Include the visible graph at its current pan/zoom and the visible portions of open detail information, preserving current attribute-folding and scroll states. Do not unfold attributes or include graph/card content outside the captured area. Capturing a transient tooltip and retaining it while the save control receives focus need explicit design assessment, not an implicit promise that a tooltip survives its normal dismissal conditions. Retained constraints: Inspect object details on h... (STV_SHR_015), Explore documentation offline (STV_SHR_017), Explore documentation on st... (STV_SHR_018), Keep long tooltips readable... (STV_SHR_033), Operate the view using the ... (STV_SHR_034), Explore multiple views inde... (STV_SHR_038), Zoom the traceability view (STV_SHR_039), Pan the traceability view (STV_SHR_040) and Keep explicitly opened arti... (STV_SHR_057) retain content, offline/static hosting, accessibility, isolation, viewport and persistence obligations. Export must not fetch unavailable remote resources or disclose hidden Needs. It does not change the live graph, card collection or rendering state. Pending impact analysis: Assess Deliver a self-contained do... (STV_SYS_003), Provide original-object ins... (STV_SYS_006), Isolate view sessions (STV_SYS_007), Publish full rendered details (STV_SWR_015), Avoid runtime network loading (STV_SWR_017), Use portable output URLs (STV_SWR_018), Constrain and retain detail... (STV_SWR_033), Implement view-local zoom (STV_SWR_039), Implement view-local pan (STV_SWR_040), Preserve static third-party... (STV_SWR_049), Own a per-view persistent d... (STV_SWR_063), Present and focus persisten... (STV_SWR_064) and Accessible view and viewport (STV_SWE_RENDER). Reconcile clipping/composition, typography, local media, safe serialization, standalone SVG readability, keyboard activation and cancel/failure behavior. Assess technology/license implications before selecting an export library. See Internal interfaces and model contract, Technology stack and dependency decisions, Architecture Design Decisions and Implementation verification plan. Open feasibility/scope points: Browser and OS download policies may not permit an application-controlled location picker, especially under file URLs or mobile browsers. The requested location choice is retained as intent; silently substituting a fixed download folder is not an approved exception. Decide supported save interactions and any platform exception with the owner before concept acceptance. Toolbar inclusion and transient-tooltip capture semantics also remain explicit refinement questions. No implementation mechanism, browser API, raster-only substitute or new platform qualification is selected by this CR. Stakeholder-stage intake history (before owner approval): exact requirement approval and downstream refinement are pending. No internal requirements, ADRs, cases, code or verification states have been changed. Actual checks and limitations are consolidated in Project maturity. Current decision: The owner accepted this CR and its exact stakeholder requirement on 2026-10-25 and requested concept creation. Concept design, current readiness and actual checks are centralized in Project maturity; earlier intake-stage pending-work statements above describe the prior stage. Owner save clarification, 2026-10-25: Use browser-managed Save As with documented settings, including enabling a location prompt when downloads otherwise go to a default directory. An application-controlled folder picker is not required. This resolves the location-feasibility choice, not runtime verification. |