GFItemsCarousel rowcount bigger than images.length
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- dart, flutter
- Domain
- frontend, mobile-dev
Research direction
Start by reproducing GFItemsCarousel with rowCount set to 5 and three children, then inspect the GFItemsCarousel implementation and its drag or scrolling behavior. Done means dragging this configuration no longer causes rapid flashing or leaves the carousel with an incorrect offset, while the expected scrolling behavior is preserved.
Written by the indexing model from the issue text.
Description
Describe the bug
Currently there is a bug if the row count is bigger than the children itself. The ui is fine but when you start to drag, the ui will flashing faster (it's going left and right very fast) and the it eventually will stop and it will make the offset very weird.
To Reproduce
Steps to reproduce the behavior:
final List<String> imageList = [
"https://cdn.pixabay.com/photo/2017/12/03/18/04/christmas-balls-2995437_960_720.jpg",
"https://cdn.pixabay.com/photo/2017/12/13/00/23/christmas-3015776_960_720.jpg",
"https://cdn.pixabay.com/photo/2019/12/19/10/55/christmas-market-4705877_960_720.jpg",
];
GFItemsCarousel(
rowCount: 5,
children: imageList.map(
(url) {
return Container(
margin: EdgeInsets.all(5.0),
child: ClipRRect(
borderRadius: BorderRadius.all(Radius.circular(5.0)),
child:
Image.network(url, fit: BoxFit.cover, width: 1000.0),
),
);
},
).toList(),
),
- As per code block above, the row must be higher than the number of children
- Based on the screenshot above, the green color box will be initial display. When the user scroll or drag the carousel, the red color box highlighted the bug happened
Expected behavior
Is either disabling the animation or physic scrolling.
- Dominant language
- Dart
- Stars
- 4.8k
- Forks
- 649
- PR merge metrics
- No merged PRs in 30d
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.
More from ionicfirebaseapp/getwidget
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ionicfirebaseapp/getwidget#378 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
ionicfirebaseapp/getwidget#377 ·
-
GFToggle Open
Difficulty 3/5 1-2 days Newbie friendliness 20/100
ionicfirebaseapp/getwidget#355 ·
-
GfDatePicker Open
Difficulty 4/5 3-5 days Newbie friendliness 15/100
ionicfirebaseapp/getwidget#353 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ionicfirebaseapp/getwidget#352 · 1 comment ·
All issues in ionicfirebaseapp/getwidget
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
from.page-issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
[Super Editor][Chat] - Floating editor scaffold does not reset panel height after closing panel Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
a2ui-project/a2ui#2763 ·