This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Expose Autofill Setting to all builds on next merge day #11320
Labels
Comments
We can do this now! |
ekager
added a commit
to ekager/fenix
that referenced
this issue
Jul 2, 2020
ekager
added a commit
to ekager/fenix
that referenced
this issue
Jul 2, 2020
ekager
added a commit
to ekager/fenix
that referenced
this issue
Jul 2, 2020
ekager
added a commit
to ekager/fenix
that referenced
this issue
Jul 2, 2020
ekager
added a commit
that referenced
this issue
Jul 3, 2020
This is done 🆗 |
data-sync-user
changed the title
Expose Autofill Setting to all builds on next merge day
FNX3-14551 ⁃ Expose Autofill Setting to all builds on next merge day
Aug 10, 2020
data-sync-user
changed the title
FNX3-14551 ⁃ Expose Autofill Setting to all builds on next merge day
FNX-12230 ⁃ Expose Autofill Setting to all builds on next merge day
Aug 11, 2020
data-sync-user
changed the title
FNX-12230 ⁃ Expose Autofill Setting to all builds on next merge day
FNX2-13425 ⁃ Expose Autofill Setting to all builds on next merge day
Aug 11, 2020
data-sync-user
changed the title
FNX2-13425 ⁃ Expose Autofill Setting to all builds on next merge day
Expose Autofill Setting to all builds on next merge day
May 18, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In #8967 I exposed the autofill login setting (separate from the save login setting) for Nightly users because here is a new GV runtime setting for loginAutofillEnabled so we can now stop conflating the two settings. On the next GV merge day, let's expose this for all users.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: