microsoft / microsoft/react-native-windows
Documenting differences between RNW and RN Win32
Open
Nobody has claimed this yet.
Documentation
enhancement
Platform: NetUI
Workstream: Developer Experience
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Opening this issue to collect documentation of areas that are forked or have different behaviors between RNW and RNWin32. As RN Win32 turns toward aligning with RNW, we want to make sure that we are addressing any functionality differences or gaps that we will encounter.
- enableFocusRing default behavior (false for win32 and true for windows).
- ImageLoader.getSize uses a callback instead of a promise in win32
- Accessibility gaps probably exist (i.e. accessibilityAccessKey)
@acoates-ms FYI
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the differences listed between RNW and RN Win32: enableFocusRing defaults, ImageLoader.getSize callback versus promise behavior, and accessibility gaps such as accessibilityAccessKey. Done means documenting the relevant functionality differences and gaps so alignment work can address them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100