FA-54759 / Accessibility interaction semantics / Member archive

Fragment identifiers enter the fallback document name · case 04

Fragment identifiers enter the fallback document name.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Input document record title,url,language,mime,loaded,percent,security,private,permissions,revision. Return name (title else URL basename stripping query and fragment), address (None if private), language (replace underscore with hyphen), content_type (lowercase MIME before semicolon), loading (not loaded), progress (100 if loaded otherwise clamp integer percent0..99), secure (security exactly verified), actions (print then copy only when each permission and loaded; copy also forbidden in private), revision. Empty URL fallback is empty name. This policy is deliberately stipulated for a document accessibility bridge.

Why this case matters

Offline accessibility bridge model with explicit policy; useful for testing semantic API adapters independently of browser implementations.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
contract fixture 5	`{"actions": [], "address": "https://x/path/#frag", "content_type": "text/xml", "language": "en", "loading": false, "name": "#frag", "progress": 100, "revision": 4, "secure": true}`	`{"actions": [], "address": "https://x/path/#frag", "content_type": "text/xml", "language": "en", "loading": false, "name": "path", "progress": 100, "revision": 4, "secure": true}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.