[0.88] Skip clear text backgrounds to restore Japanese IME underlines
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react-native
- Domain
- mobile
Research direction
The issue identifies a one-file backport of commit 0bd33261d1e519f319c3225247879273c5a2a709, already prepared as PR #59432. Read that commit and compare it with the 0.88-stable branch; the target is to omit the default clear text background while preserving the described text and event metadata. Confirm the backport applies cleanly and check the supplied iOS reproducer for the Japanese IME composition underline.
Written by the indexing model from the issue text.
Description
Target Branch
0.88
Link to commit or PR to be picked
https://github.com/react/react-native/commit/0bd33261d1e519f319c3225247879273c5a2a709
Description
Please consider picking the already-landed #59207 change into 0.88. The current 0.88-stable branch still emits the default clear text background; main omits it. The change is an exact, conflict-free, one-file backport.
Additional motivation beyond the upstream text-rendering optimization: a native iOS 27 experiment with React Native's actual backing views and delegate adapters shows that this clear background attribute hides the Japanese IME composition underline. Omitting it restores the underline while preserving the same foreground, font, default shadow and EventEmitter metadata. The multiline input fails both from empty and with existing attributed text; the single-line input fails with existing attributed text. All four cases display the underline when the background attribute is omitted.
This request concerns the composition indicator. It does not claim to fix all CJK input synchronization failures. No full React Native app or physical-device test was run for this backport; the native experiment and the upstream author's full RNTester validation are distinguished in the PR.
Prepared backport: https://github.com/react/react-native/pull/59432
Reproducer and screenshots: https://github.com/riottt/react-native/tree/evidence/ios-japanese-ime-0.88
- Dominant language
- JavaScript
- Stars
- 429
- Forks
- 11
- Avg merge
- 4h 13m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from reactwg/react-native-releases
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
reactwg/react-native-releases#1491 ·
-
Type Pick Request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
reactwg/react-native-releases#1487 · 1 comment ·
-
Type Pick Request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
reactwg/react-native-releases#1472 · 1 comment ·
-
Type Pick Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
reactwg/react-native-releases#1435 · 1 comment ·
-
Type Pick Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
reactwg/react-native-releases#1427 · 1 comment ·
All issues in reactwg/react-native-releases
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mailgun/mailgun.js#544 ·
-
beginner bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
BistaDinesh03/critique#266 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
solana-foundation/solana-web3.js#4015 · 1 comment ·
Maintainers usually reply within 1 day
-
area: dependencies auto-generated cwe: 405 dependencies ecosystem: npm help wanted package: minimatch scope: runtime security security-alert severity: medium source: dependabot supply-chain vulnerability
Difficulty 2/5 Half a day Newbie friendliness 65/100
tdk-landscape/tdk-cli-core#2811 ·
-
a11y bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-webui/open-webui#33442 · 2 comments ·
Maintainers usually reply within 1 day