iOS Incorrect width calculation in iOS DateTimePicker inside views with absolute positioning
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- ios, javascript, react-native
Direzione di ricerca
Start by reproducing the width mismatch using the provided DateTimePicker example inside an absolutely positioned View on iOS with React Native 0.76.9 and the new architecture enabled. Then trace how the iOS picker measures its width in that layout; done means it expands to the parent’s 100% width while retaining the reported behavior in a regular view. The issue names no source files or tests, so finding the relevant implementation and regression coverage will require exploring the project.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Bug report
Summary
Can't resize RNDateTimePicker component to 100% in position: absolute views after upgrading react-native to 0.76.9 version. Also see that generally DateTimePicker not stable with new react-native architecture.
Reproducible sample code
If i just render this time picker inside screen:
<DateTimePicker
mode={'time'}
locale='en-EN'
value={new Date()}
style={{ width: '100%', height: 200 }}
onChange={() => {}}
textColor={'white'}
display={'spinner'}
/>
Everything works fine, but If i render this picker inside some position absolute view I see that picker width is default and I can't fit to parent width (incorrect width calculating):
<View
style={{
position: 'absolute',
left: 0,
right: 0,
top: 600,
zIndex: 100,
height: 200,
width: '100%',
backgroundColor: 'green',
}}
>
<DateTimePicker
mode={'time'}
locale='en-EN'
value={new Date()}
style={{ width: '100%', height: 200, backgroundColor: 'gray' }}
onChange={() => {}}
textColor={'white'}
display={'spinner'}
/>
</View>
Steps to reproduce
- Place DateTimePicker inside
position: absoluteview - Component doesn't fit correctly to parent's width
Describe what you expected to happen:
- Place DateTimePicker inside
position: absoluteview - Should resize to 100% of parent's width
Environment info
npx react-native info output:
System:
OS: macOS 15.3.2
CPU: (12) arm64 Apple M2 Max
Memory: 104.30 MB / 32.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 18.20.3
path: ~/.nvm/versions/node/v18.20.3/bin/node
Yarn:
version: 1.22.19
path: /opt/homebrew/bin/yarn
npm:
version: 10.7.0
path: ~/.nvm/versions/node/v18.20.3/bin/npm
Watchman:
version: 2024.12.02.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /Users/eduarddunda/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.2
- iOS 18.2
- macOS 15.2
- tvOS 18.2
- visionOS 2.2
- watchOS 11.2
Android SDK:
API Levels:
- "30"
- "31"
- "32"
- "33"
- "34"
- "35"
Build Tools:
- 30.0.2
- 30.0.3
- 32.0.0
- 33.0.0
- 33.0.1
- 34.0.0
- 35.0.0
System Images:
- android-31 | ARM 64 v8a
- android-33 | Google APIs ARM 64 v8a
- android-33 | Google Play ARM 64 v8a
- android-34 | Google APIs ARM 64 v8a
- android-34 | Google Play ARM 64 v8a
- android-35 | Google APIs ARM 64 v8a
- android-35 | Google Play ARM 64 v8a
Android NDK: 22.1.7171670
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12550806
Xcode:
version: 16.2/16C5032a
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.14
path: /Users/eduarddunda/.sdkman/candidates/java/current/bin/javac
Ruby:
version: 2.7.6
path: /Users/eduarddunda/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli":
installed: 15.0.1
wanted: 15.0.1
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.76.9
wanted: 0.76.9
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
datetimepicker version: 8.4.1
iOS / Android version: iOS 17.5 Simulator
P.S
Screenshot with example:
- picker picker is general component render
- second picker is wrapper inside absolute positioned view
Screenshot
- Lingua principale
- JavaScript
- Stelle
- 2.9k
- Fork
- 459
- Merge medio
- 4g 16h
- PR unite (30g)
- 5
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di react-native-datetimepicker/datetimepicker
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 58/100
react-native-datetimepicker/datetimepicker#1070 · 1 commento ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 52/100
-
DateTimePickerAndroid.open() throws "Cannot read property" error on RN 0.78.3 new architectureAperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
react-native-datetimepicker/datetimepicker#1047 · 6 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 20/100
react-native-datetimepicker/datetimepicker#1046 · 1 commento ·
Tutte le issue di react-native-datetimepicker/datetimepicker
Issue simili
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 87/100
OWASP/CheatSheetSeries#2905 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
ComposioHQ/composio#5249 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
zilliztech/memsearch#838 ·
I maintainer di solito rispondono entro 1 giorno
-
[DOCS] Nine one-colon directives hide code examples and notes in the reference docs (e.g. CustomJS)ApertaTRIAGE
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
cdx-audit output written to a pipe is cut off at 64 KiBForse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Apertabug mode:cli
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
I maintainer di solito rispondono entro 1 giorno