Update Compose Graphics to support Wide Color Gamut + HDR [379135036]

Fixed

Bug

Status Update

No update yet.

Description

nj...@google.com

created issue #1

Nov 14, 2024 07:17PM

Currently consumption of Color instances converts the color long to an int via the toArgb API

internal fun NativePaint.setNativeColor(value: Color) {
    this.color = value.toArgb()
}

Instead on supported Android platform levels, we should consume the Color long directly with the following:

internal fun NativePaint.setNativeColor(value: Color) {
    if ((value.value and 0x3fUL) == 0UL || Build.API_LEVEL < 29) {
        this.color = value.toArgb()
    } else {
        this.color = value
    }
}

Comments

ap...@google.com <ap...@google.com> #2Nov 22, 2024 07:23PM

Marked as fixed.

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

pr...@google.com <pr...@google.com> #3Dec 11, 2024 06:27PM

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

to...@gmail.com <to...@gmail.com> #4Jan 7, 2025 07:21AM

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

Issue 379135036

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Nov 22, 2024 07:23PM

pr...@google.com <pr...@google.com> #3Dec 11, 2024 06:27PM

to...@gmail.com <to...@gmail.com> #4Jan 7, 2025 07:21AM

Add comment

Issue metadata