-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ion-item-sliding class active-options-left/right is not always applied leading into buttons not being rendered #11988
Comments
Ahh, interesting find! Unfortunately, i have not been able to reproduce this issue, would you mind sharing a minimal repo we could use to reproduce this? |
I will give it a try, but not sure I will be able to make a repo as complex as the actual case. Interesting fact, in my repo I see these warning in the console when sliding an item with x20 CPU slowdown:
Whereas in a simplistic repo trying to reproduce this I only see:
If I remove the CPU slowdown both repos show only the violation warning once per slide. Does this help at all? |
OK I managed to reproduce it in the ionic repo tests. I also made a video demonstrating the issue in this repo |
@jgw96 are you still not able to reproduce this or just didn't get the chance to update this issue? |
Hey @masimplo , Sorry have been very busy with getting the latest release ready (: Would you be able to try the latest nightly and see if you can still reproduce this issue? It seems to be working fine for me (: |
@jgw96 I know you guys are all over the place these days, but are doing a great job on the latest releases! Unfortunately, the issue is still happening even in nightly. Don't understand how you are not able to reproduce it. I have tried the repo in 3-4 different machines (and a bunch of phones) and is happening every single time. Did you try to enable CPU throttling in chrome as in faster machines is harder to reproduce without it. I updated the branch of my ionic-fork with the latest version from master and made a little screencast demonstrating the issue. Please have a look again. To run the example test run the sliding-item virtual scroll tests as usual |
@manucorporat this issue is happening on Ionic 2.x can we expect a fix for it as well? |
it works after i use this style in .scss file: |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Ionic version: (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ... (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Sliding ion-options sometimes does not show buttons but empty space. Sliding the item back and forth a bit shows the buttons.
Expected behavior:
Sliding ion-options should always display the buttons underneath.
Steps to reproduce:
My exact case is a virtual scroll list that renders custom components that wrap an ion-item-sliding but should be reproducible in simpler examples.
In a list rendering ion-item-sliding slide the item left or right in a slow device or using chrome dev tools CPU throttling (seems to be a race condition of some kind).
Some times buttons will appear, some times a white area will appear instead of the buttons until you
nudge the item again a bit.
When buttons appear DOM looks like
When buttons do not appear DOM looks like:
Notice that in the second case the class
active-options-left
is missing, althoughactive-slide
is presentOther information:
Have tested this in 3.1.0, 3.3.0 and latest nightly and consistently happens across all.
Ionic info: (run
ionic info
from a terminal/cmd prompt and paste output below):Note: a similar issue had been filed for an older version of Ionic but was closed due to lack of reporter feedback. I have commented both on the closed issue, but opened a new updated issue, so this doesn't fall between the cracks.
The text was updated successfully, but these errors were encountered: