Repository navigation
Add imperative vibration API and device verification controls - #30
Merged
Merged
Conversation
This was referenced Oct 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Semantic controllers cannot request browser feedback through the component API. Add
canTriggerHaptic()andtriggerHaptic()with the component's vibration presets, custom patterns, duration cap, and intensity modulation. Requests resolve explicit acceptance/failure results, use current browser capabilities, and create no auxiliary DOM.iOS imperative ticks remain unavailable, including during transient activation. WebKit's trusted-event enforcement (WebKit/WebKit@fc1ef83) rejects script-generated label activation. A successful browser vibration request is also explicitly distinguished from observed tactile output.
Related to #27. This completes its browser API work; the proposed native imperative route and physical-device requirements remain open. #7/#9 and the full-certification tracker #1 must stay open without the required physical and VoiceOver observations.
Add synchronous, awaited, and timer examples to the live documentation, update the physical-device procedure, and mark the API unreleased (published 0.1.0 does not contain these exports).
Validation: 132 tests with 100% runtime coverage; React 18/19 matrix; ESM/CommonJS, SSR, declarations and isolated packed consumers; bundle 4516 gzip bytes within 8192-byte budget; six Chromium/WebKit library tests; 27 documentation checks including imperative acceptance, rejection and iOS fallback; documentation typecheck, static build and snippet checks; lint.