ionic-team / ionic-team/ionic-framework
bug: datetime, scrolling two columns at once causes scroll position to be reset
- Ngôn ngữ chính
- TypeScript
- Star
- 52.7k
- Fork
- 13.3k
- Merge trung bình
- 1 ngày 15 giờ
- Pull request đã merge (30 ngày)
- 51
Mô tả
### Prerequisites
- [X] I have read the [Contributing Guidelines](https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#creating-an-issue).
- [X] I agree to follow the [Code of Conduct](https://ionicframework.com/code-of-conduct).
- [X] I have searched for [existing issues](https://github.com/ionic-team/ionic-framework/issues) that already report this problem, without success.
### Ionic Framework Version
- [ ] v4.x
- [ ] v5.x
- [X] v6.x
- [ ] Nightly
### Current Behavior
I think the video shows the issue pretty well. While its not broken, I feel like the UX isn't ideal.
### Video showcasing the blipping, or visual feedback is like "Whoa what just happened there"
```
```
https://user-images.githubusercontent.com/7741481/184932558-fe840d75-329e-4ff0-84d0-2dcf4e927a46.mov
### Expected Behavior
No visual blipping
### Steps to Reproduce
Unless there are some undocumented requirements for `IonDatetime`, the setup in my use case is just using it within an `IonApp`. No `IonContent`, `IonPage`, whatever.
Repro is simply to render the `IonDatetime` component, and then attempt to move wheels at the same time. Basically, don't wait for one wheel to stop before trying to move another.
### Code Reproduction URL
_No response_
### Ionic Info
Ionic: 6.2.2
Safari: 15.5
iPhone: 8
mode: `ios`
### Additional Information
_No response_
Hướng dẫn đóng góp
Hướng nghiên cứu
Start with the IonDatetime component and reproduce the issue on the reported iPhone/Safari setup by moving both wheels before either stops. Trace the scrolling and position updates, then verify that simultaneous two-column scrolling no longer causes a visible reset or blip.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Đánh giá
- Công nghệ
- typescript
- Lĩnh vực
- frontend, mobile-dev
- Loại issue
- Lỗi
- Độ khó
- 3/5
- Thời gian dự kiến
- 1-2 ngày
- Mức độ hoạt động
- Đình trệ
- Độ rõ ràng
- Khá rõ ràng
- Mức phù hợp với người mới
- 35/100