Infeasible
Status Update
Comments
xa...@gmail.com <xa...@gmail.com> #2
Same issue with version 26.0.1
st...@gmail.com <st...@gmail.com> #3
how fix this issue ? on pre-lollipop only.
tm...@gmail.com <tm...@gmail.com> #4
In my case (pre-lollipop, support library 26.0.1), I'm noticing this issue only when SwipeRefreshLayout is nested within CoordinatorLayout (which is passed as target view for Snackbar.make(...)).
With "Show layout bounds" option enabled in developer options, it is revealed that SnackbarLayout is nested within another View which has correct position (Screenshot1 and Screenshot2).
Swiping on SwipeRefreshLayout puts the SnackbarLayout in correct position (Screenshot3).
With "Show layout bounds" option enabled in developer options, it is revealed that SnackbarLayout is nested within another View which has correct position (Screenshot1 and Screenshot2).
Swiping on SwipeRefreshLayout puts the SnackbarLayout in correct position (Screenshot3).
tm...@gmail.com <tm...@gmail.com> #5
Supplementary info: as you can see in my previous screenshots, FloatingActionButton is being used. With FAB removed, issue is still present.
tm...@gmail.com <tm...@gmail.com> #6
Oh well ... a stupid workaround:
1. SwipeRefreshLayout.setEnabled(false)
2. Snackbar.make(...).show()
3. SwipeRefreshLayout.setEnabled(true)
1. SwipeRefreshLayout.setEnabled(false)
2. Snackbar.make(...).show()
3. SwipeRefreshLayout.setEnabled(true)
yu...@gmail.com <yu...@gmail.com> #7
It seems to work well! Thank you, but still be waiting for the fix from the android dev team.
[Deleted User] <[Deleted User]> #8
> I'm noticing this issue only when SwipeRefreshLayout is nested within CoordinatorLayout (which is passed as target view for Snackbar.make(...)).
I'm experiencing the same issue even on the screens without coordinator layout or swipeToRefreshLayout.
Use postDelayed with 200ms delay for showing snackbar. Worked for me
I'm experiencing the same issue even on the screens without coordinator layout or swipeToRefreshLayout.
Use postDelayed with 200ms delay for showing snackbar. Worked for me
eu...@gmail.com <eu...@gmail.com> #9
i'm facing this bug with CoordinatorLayout without swipeToRefreshLayout..
some hacks above seems didn't work for me, still wait for fix, hopefully.
some hacks above seems didn't work for me, still wait for fix, hopefully.
ha...@gmail.com <ha...@gmail.com> #10
SwipeRefreshLayout.setEnabled(false)
then
post delay 200ms
work for me
then
post delay 200ms
work for me
ar...@google.com <ar...@google.com> #11
Can you please provide the below requested information to better understand the issue:
Android build
Which Android build are you using? (e.g. KVT49L)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
Please provide source code or apk of a sample application to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
Android build
Which Android build are you using? (e.g. KVT49L)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
Please provide source code or apk of a sample application to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
ar...@gmail.com <ar...@gmail.com> #12
We observe the same issue. The sample project, package and video are in the attachments.
I believe this is a regression in Support 26.+. Looks like "OnApplyWindowInsetsListener" is not being invoked with default value or something like that. Please notice that this can happen with Toolbar as well (sometimes).
Frequency — 100 % of the time.
Expected output — snackbar being on the bottom of the screen.
Current output — snackbar a bit on top of the bottom of the screen.
Configuration
* Support — 26.1.0
* Minimum SDK — 19
* Target SDK — 26
Device
* LG D855
* Android 4.4.2
I believe this is a regression in Support 26.+. Looks like "OnApplyWindowInsetsListener" is not being invoked with default value or something like that. Please notice that this can happen with Toolbar as well (sometimes).
Frequency — 100 % of the time.
Expected output — snackbar being on the bottom of the screen.
Current output — snackbar a bit on top of the bottom of the screen.
Configuration
* Support — 26.1.0
* Minimum SDK — 19
* Target SDK — 26
Device
* LG D855
* Android 4.4.2
ar...@google.com <ar...@google.com> #13
We have shared this with our engineering team and will update this issue with more information as it becomes available.
ch...@beyls.net <ch...@beyls.net> #14
I was able to reproduce this issue on Android 4.1, 4.2, 4.3 and 4.4.
Showing a Snackbar in a simple CoordinatorLayout in onStart() is enough to trigger it.
Attached is a minimal sample project I created to demonstrate this.
Showing a Snackbar in a simple CoordinatorLayout in onStart() is enough to trigger it.
Attached is a minimal sample project I created to demonstrate this.
ch...@beyls.net <ch...@beyls.net> #15
Any update ? This issue is still present in support libraries 27.0.2 and it's really annoying.
al...@gmail.com <al...@gmail.com> #16
That's correct, still present in support libraries 27.0.2 Any new updates?
zi...@gmail.com <zi...@gmail.com> #17
any update? i am zenfone 4 kitkat..
it become wrong when i put swipe layout to my coordinator layout
it become wrong when i put swipe layout to my coordinator layout
al...@gmail.com <al...@gmail.com> #18
Still present in support libraries 27.1.0 Any new updates?
i....@gmail.com <i....@gmail.com> #19
Why Google ignores it?
ma...@matthew-perkins.com <ma...@matthew-perkins.com> #20
Will this be receiving a fix at any point?
jo...@gmail.com <jo...@gmail.com> #21
Still seeing this in 27.1.1
mi...@cncenter.cz <mi...@cncenter.cz> #22
Same here. Using support libraries 27.1.1 I can see this issue on all Android 4.x devices.
be...@gmail.com <be...@gmail.com> #23
It looks this has been fixed on 28 with Material Theme.
is...@google.com <is...@google.com>
hr...@gmail.com <hr...@gmail.com> #24
Did anyone solve the problem ?
m....@gmail.com <m....@gmail.com> #25
#23: Can you be more specific please? Thank you.
mr...@gmail.com <mr...@gmail.com> #26
Adding a ```.addCallback(object : BaseTransientBottomBar.BaseCallback<Snackbar>() {
override fun onShown(transientBottomBar: Snackbar) {
}
})```
Fixed the problem on per-lolipop devices
override fun onShown(transientBottomBar: Snackbar) {
}
})```
Fixed the problem on per-lolipop devices
ch...@beyls.net <ch...@beyls.net> #27
Using the classic AppCompat themes, the bug is still present in the latest version of Material Components (1.1.0-alpha05). Adding an empty callback doesn't change anything for me on pre-Lollipop devices.
Using the new Theme.MaterialComponents.* themes, the Snackbar now looks more like a Toast and doesn't "slide" anymore. In that configuration the Snackbar always positions itself properly on pre-Lollipop devices.
I think the new Snackbar doesn't look as smooth as the classic one but at least it works as intended.
Using the new Theme.MaterialComponents.* themes, the Snackbar now looks more like a Toast and doesn't "slide" anymore. In that configuration the Snackbar always positions itself properly on pre-Lollipop devices.
I think the new Snackbar doesn't look as smooth as the classic one but at least it works as intended.
em...@google.com <em...@google.com> #28
This appears to be a bug in Material Design Components, not Jetpack (androidx
). If this bug is still occurring, please re-file it on the MDC issue tracker:
Description
Version used: 26.0.0
Theme used: AppCompat
Devices/Android versions reproduced on: Android 4.4.2 (and the other versions of android 4x)
Code to trigger the issue:
```Snackbar.make(view, message, length).show()```
Some screen attached: