Fixed
Status Update
No update yet.
Comments
au...@google.com
[Deleted User] <[Deleted User]>
I am experiencing this too...
ca...@gmail.com
Another workaround might help
handler.postDelayed(new Runnable() {
@Override
public void run() {
initiateRefresh();
}
}, 1000);
handler.postDelayed(new Runnable() {
@Override
public void run() {
initiateRefresh();
}
}, 1000);
mm...@gmail.com
same problem here.
we...@gmail.com
Same issue here. I am calling an AsyncTask (that calls setRefreshing) from onResume.
[Deleted User] <[Deleted User]>
Same here. android.support.v4 v 21.0.0
[Deleted User] <[Deleted User]>
Problem still exists with android.support.v4:21.0.3.
un...@gmail.com
FWIW: a workaround that seems to work (even without the delay):
final boolean refreshing = true;
swipeToRefreshLayout.post(new Runnable() {
@Override public void run() {
swipeToRefreshLayout.setRefreshing(refreshing);
}
});
final boolean refreshing = true;
swipeToRefreshLayout.post(new Runnable() {
@Override public void run() {
swipeToRefreshLayout.setRefreshing(refreshing);
}
});
se...@gmail.com
[Comment deleted]
se...@gmail.com
[Comment deleted]
si...@gmail.com
The same problem.
[Deleted User] <[Deleted User]>
The post() workaround works when loading programmatically, but the gesture down is still broken.
de...@gmail.com
It seems the gesture doesn't work if the view doesn't have a ScrollView widget in its hierarchy.
jf...@gmail.com
My solution is to override SwipeRefreshLayout
private boolean mMeasured = false;
private boolean mPreMeasureRefreshing = false;
@Override
public void onMeasure(int widthMeasureSpec, int heightMeasureSpec) {
super.onMeasure(widthMeasureSpec, heightMeasureSpec);
if (!mMeasured) {
mMeasured = true;
setRefreshing(mPreMeasureRefreshing);
}
}
@Override
public void setRefreshing(boolean refreshing) {
if (mMeasured) {
super.setRefreshing(refreshing);
} else {
mPreMeasureRefreshing = refreshing;
}
}
private boolean mMeasured = false;
private boolean mPreMeasureRefreshing = false;
@Override
public void onMeasure(int widthMeasureSpec, int heightMeasureSpec) {
super.onMeasure(widthMeasureSpec, heightMeasureSpec);
if (!mMeasured) {
mMeasured = true;
setRefreshing(mPreMeasureRefreshing);
}
}
@Override
public void setRefreshing(boolean refreshing) {
if (mMeasured) {
super.setRefreshing(refreshing);
} else {
mPreMeasureRefreshing = refreshing;
}
}
[Deleted User] <[Deleted User]>
Still broken, v22.2.0
ha...@gmail.com
Please, fix this issue.
sr...@gmail.com
Still exists with 22.2.1
la...@gmail.com
Still an issue with 23.0.0
ja...@gmail.com
Still broken in 23.0.1
hi...@gmail.com
I don't think this is broken in Google's eyes.
"The refresh indicator appears only in conjunction with a refresh gesture or action. Syncing does not display a refresh indicator."
http://www.google.com/design/spec/patterns/swipe-to-refresh.html#swipe-to-refresh-swipe-to-refresh
"The refresh indicator appears only in conjunction with a refresh gesture or action. Syncing does not display a refresh indicator."
dr...@gmail.com
Note that this almost year old bug has not been triaged yet, meaning they didn't see it, or choose to ignore.
I couldn't find any recommended way to display initial loading. Empty view is for empty list, having a separate loading indicator and a swipe-to-refresh indicator is problematic to code and may confuse the user. In Google's world everything shows up immediately.
Note that even the GMail app shows two indicators sometimes. In the morning when I turn WiFi on, it starts syncing, but it takes a while, and if in the middle of that I swipe to refresh it shows me two spinners, going in opposite directions.
I couldn't find any recommended way to display initial loading. Empty view is for empty list, having a separate loading indicator and a swipe-to-refresh indicator is problematic to code and may confuse the user. In Google's world everything shows up immediately.
Note that even the GMail app shows two indicators sometimes. In the morning when I turn WiFi on, it starts syncing, but it takes a while, and if in the middle of that I swipe to refresh it shows me two spinners, going in opposite directions.
ca...@gmail.com
Why hasn't this been fixed already??
gr...@gmail.com
[Comment deleted]
mw...@gmail.com
What google is doing ??????
Still not fixed
Still not fixed
Description
Version used: 25.1.0
Theme used: Theme.AppCompat.NoActionBar
Devices/Android versions reproduced on: 4.1.1 and 7.0
Hey guys, I was testing my app with the Support Library 25.1.0 and found this bug on the TextInputLayout. If the EditText or TextInputEditText inside the TextInputLayout sets text using android:text, the hint and text overlay (Like this:
*Steps to reproduce: *
1. Add a TextInputLayout from the Design library;
2. Add an EditText or TextInputEditText inside it with a hint set;
3. Run the app and notice everything works;
4. Set an android:text value attribute in the EditText
5. Run the app again and notice how the hint and the text overlay. The component doesn't fix the glitch even if the user type something.