bamlab / bamlab/react-tv-space-navigation
SpatialNavigationRoot behaviour with useLockSpatialNavigation
- Dominant language
- TypeScript
- Stars
- 319
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
When `useLockSpatialNavigation.lock()` is set, the `SpatialNavigationRoot` `onDirectionHandledWithoutMovement` callback still fires
**To Reproduce**
```tsx
const spatialNavigationLockActions = useLockSpatialNavigation();
useEffect(() => {
spatialNavigationLockActions.lock()
}, []);
...
console.log('bam')} />
```
**Expected behavior**
When the spatial navigation is locked, it would be expected that any callbacks or functionality of the navigation system are disabled.
**Version and OS**
- Library version: `5.1.0`
- React Native version: `0.72.0`
- OS [e.g. Android, web]
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating SpatialNavigationRoot and useLockSpatialNavigation, then reproduce the issue with the lock() call and the onDirectionHandledWithoutMovement callback shown in the report. Done means the callback and other navigation functionality remain inactive while spatial navigation is locked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100