OctaTouch Gesture Runtime: Smoke-Test Behavior Profile

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 13 April 2027.¶

Copyright Notice

Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.¶

Table of Contents

1. Scope and Status

This file is a candidate informational Internet-Draft source. It has not been submitted to the IETF, is not a registered Internet-Draft, and is not an RFC. It describes test expectations only. Implementations may behave differently until the complete runtime specification and source are reviewed.¶

2. Source Test Cases

The source test script imports a gesture engine, frame constructor, gesture-intent enumeration, and gesture-type enumeration from a project-relative runtime module. The following expected outcomes are encoded by assertions in that script:¶

1. A single-contact tap sequence is expected to yield type TAP and intent SELECT.¶
2. A three-finger pinch-in sequence is expected to yield type THREE_FINGER_PINCH_IN and intent COPY.¶
3. A three-finger left-swipe sequence is expected to yield type THREE_FINGER_SWIPE_LEFT and intent UNDO.¶
4. The pinch-in sequence under vehicle state driving is expected to yield intent BLOCKED_DRIVING_MODE.¶
5. A three-finger tap with screenReaderActive set to true is expected to yield type THREE_FINGER_TAP and intent BLOCKED_ACCESSIBILITY_CONFLICT.¶

These are expectations extracted from test assertions, not independently observed execution results.¶

3. Verification Requirements Before Reuse

1. Obtain the exact runtime module and dependency lockfile.¶
2. Execute the tests in the supported project environment and preserve the command, exit status, environment versions, commit identifier, and complete logs.¶
3. Specify gesture thresholds, cancellation behavior, touch identifier semantics, timing tolerance, and state precedence.¶
4. Test driving-state blocking and accessibility conflict behavior across relevant transitions and race conditions.¶
5. Review accessibility, safety, privacy, and platform-specific behavior before treating the profile as interoperable guidance.¶

4. Security and Safety Considerations

The test assertions suggest that vehicle state and screen-reader state can block otherwise valid gesture intents. Because the implementation is not available, the effectiveness of these gates is unknown. A future specification should define the trusted source, freshness, failure mode, and precedence of safety context. It should not rely on a UI-only block if an unsafe action can still be triggered through another path.¶

5. IANA Considerations

This document makes no IANA requests.¶

Author's Address