Repository navigation
Conversation
No video on this one, and the page says why: haptics are invisible and simulators do not vibrate, so a recording would show three taps and a line of text while the thing being documented stays off-screen. Instead the page ends with the three reasons you might feel nothing, ordered by how often they are the actual cause — the environment is far more likely than the wiring.
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
This branch was successfully deployed
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
1 participant
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.
Adds the Haptic page and its sidebar entry.
No video
Every other component page carries a screen recording. This one cannot: haptics are invisible, and simulators and emulators do not vibrate at all — a clip would show three taps and a line of text while the thing being documented stays off-screen. The page says that outright rather than leaving a conspicuous gap.
In its place the page ends with the three reasons you might feel nothing, ordered by how often they are actually the cause: a simulator, system haptics being off, or the native half not being registered. The first two are far more likely than the third, which is the opposite of where people start looking.
The submodule pointer moves to the registry's
haptic-componentbranch, because the sources this page includes are not on the registry'smainyet. Merge that PR first, then re-point the submodule atmainbefore merging this one:git submodule update --remote vendor/hotwire-bridge-components git commit -am "Point the registry submodule back at main"npm run buildpasses as it stands.