Obsolete
Status Update
No update yet.
Comments
tr...@gmail.com
Yup. Facing similar issue. The indicator gets hidden under the background.
ux...@gmail.com
A workaround is to call TabLayout.setBackgroundColor() at runtime instead of specifying color in xml.
p....@gmail.com
Yeah, But now status for this issue is FutureRelease. So we can wait.
[Deleted User] <[Deleted User]>
Or you can use android:background, instead of app:tabBackground
al...@android.com
mm...@gmail.com
Released in v22.2.1.
mm...@gmail.com
In my case this is still not working.
Only if i remove the tabBackground i can see the tabIndicatorColor.
I have tried as attributes:
app:tabBackground="@color/orange"
app:tabIndicatorColor="@color/yellow"
app:tabIndicatorHeight="@dimen/space_small"
and as styles:
<item name="tabBackground">@color/orange</item>
<item name="tabIndicatorColor">@color/yellow</item>
<item name="tabIndicatorHeight">@dimen/space_small</item>
Same negative result for both.
Only if i remove the tabBackground i can see the tabIndicatorColor.
I have tried as attributes:
app:tabBackground="@color/orange"
app:tabIndicatorColor="@color/yellow"
app:tabIndicatorHeight="@dimen/space_small"
and as styles:
<item name="tabBackground">@color/orange</item>
<item name="tabIndicatorColor">@color/yellow</item>
<item name="tabIndicatorHeight">@dimen/space_small</item>
Same negative result for both.
mm...@gmail.com
I can't recreate. Make sure you're using v22.2.1.
al...@android.com
My bad, you are right. I had the old 22.2.0 in a this other branch.
It works as expected now.
It works as expected now.
Description
I am already aware that the DatePickerDialog does not expose the setMinDate/setMaxDate functions of the underlying DatePicker, so it would seem that some kind of handset maker-specific modification is affecting the minDate/maxDate.
This user reports he is running a Droid x2 on Verizon running 2.2 Froyo. While we believe he is correct in his description of his device model, many users are confused about the OS version, so he may be running 2.3.
I attempted to solve this problem by adding this theme to my Activity:
<style name="profile_editor_theme">
<item name="android:endYear">2025</item>
<item name="android:startYear">1910</item>
</style>
While this theme on my activity had the intended effect of constraining the DatePickerDialog on my test devices (a Galaxy tab and an original Motorola Droid), it apparently had no effect for the user.
This issue repros for our user 100% of the time.
The correct behavior is that there should either be no limitation on the date picker, or if we have applied our theme, the limitation should me a min year of Jan 1, 1910 and max year of Dec 31 2025. We see that on our end; our user does not see that.