[Google Lens] Move Google Lens control setting to "search settings" from "ai settings"
Categories
(Firefox for Android :: Search, task)
Tracking
()
People
(Reporter: harrisono, Assigned: harrisono)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][group3])
Attachments
(2 files, 2 obsolete files)
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Comment 1•1 month ago
|
||
Comment 3•1 month ago
|
||
| bugherder | ||
| Assignee | ||
Comment 4•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D310681
Updated•1 month ago
|
Comment 5•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Setting is in wrong place, must be removed from "AI Controls" before launch in release 153
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: Low level settings movement in screens, overall settings mechanisms remain the same.
- String changes made/needed?: renaming some strings to reflect their actual use location rather than "AI controls". No strings are changed.
- Is Android affected?: yes
This patch is I think changing string IDs, I don't know if it may cause l10n issues in the 153 UI worse than that bug that is being fixed. I think we need an l10n-driver to chime in.
Camila, what do you think?
Updated•1 month ago
|
Updated•1 month ago
|
Backed out from beta as landing this patch conflicts with landing bug 2052999.
harrisono, it seems that the l10n linter errors are because you are adding here strings that you use in bug 2052999 but you didn't stack these 2 patches to land together. Morever, it seems that you are adding the same 2 strings in the 2 patches. Could you update your patches and stack your commits so as that they land together without merge conflicts for our last beta on Wednesday? Thanks
Comment 10•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Setting is in wrong place, must be removed from "AI Controls" before launch in release 153
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: Low level settings movement in screens, overall settings mechanisms remain the same.
- String changes made/needed?: renaming some strings to reflect their actual use location rather than "AI controls". No strings are changed.
- Is Android affected?: yes
| Assignee | ||
Comment 11•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D310681
Comment 12•1 month ago
|
||
Okay from the L10N front with latest changes
Comment 13•1 month ago
|
||
Sorry. Accidentally removed the needinfo flag for harrisono with my comment. Re-adding flag here just in case.
| Assignee | ||
Comment 14•1 month ago
|
||
ok I'll work on trying to get these patches in line
Comment 15•1 month ago
|
||
Verified as fixed on the latest Firefox for Android Nightly 154.0a1 from 7/13 using a Pixel 6 (Android 17), and a Huawei Pura 70 (Android 12).
If the option is disabled, the Google Lens is replaced with the QR code icon.
When the option is enabled, the Google Lens icon is available.
Updated•1 month ago
|
Comment on attachment 9606730 [details]
Bug 2047747 - Move Google Lens integration on off setting to Search settings page
This is too late for uplift now as we are building 153.0 today.
Comment on attachment 9607269 [details]
Bug 2047747 - Move Google Lens integration on off setting to Search settings page
This is too late for uplift now as we are building 153.0 today.
Updated•19 days ago
|
Updated•15 days ago
|
Updated•4 days ago
|
Description
•