Introduce a new policy that maps directly to the AI controls
Categories
(Firefox :: Enterprise Policies, enhancement, P3)
Tracking
()
People
(Reporter: mkaply, Assigned: mkaply)
References
Details
Attachments
(3 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
In order to make things more clear, I'm going to introduce a new policy that maps directly to the AI Controls.
It will take precedence over any existing policy (translation, GenerativeAI).
It will also control the switch (The GenerativeAI policy doesn't do that)
| Assignee | ||
Comment 1•4 months ago
|
||
Updated•4 months ago
|
Backed out for causing multiple BC and XPC failures
| Assignee | ||
Comment 5•4 months ago
|
||
Sorry, couldn't get try to work. I've tested everything now.
Comment 7•4 months ago
|
||
| bugherder | ||
Comment 8•4 months ago
|
||
Did you intend for this to make 150 and/or how would you feel about uplifting this? I'm aware there's a single string for the policy description...
| Assignee | ||
Comment 9•4 months ago
|
||
Yes. String is not a huge deal. We allow policies to be English only. (Plus we're going to have to do it in a dot release for the new IPProtection policy)
| Assignee | ||
Comment 10•4 months ago
|
||
[Tracking Requested - why for this release]:
I'm getting pushback from enterprise folks that this didn't make 149. Since we're going to need the IPProtection policy as well, we should take this.,
I need to rebase though.
Updated•4 months ago
|
Updated•4 months ago
|
Comment 11•4 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Enterprises really need this and it missed 149 unfortunately.
- Code covered by automated testing?: no
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: medium
- Explanation of risk level: Changes some internal naming of some functions in AI controls, but has been thoroughly tested
- String changes made/needed?: Yes, but policy only.
- Is Android affected?: no
| Assignee | ||
Comment 12•4 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D286342
| Assignee | ||
Comment 13•4 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D286342
Updated•4 months ago
|
Comment 14•4 months ago
|
||
firefox-release Uplift Approval Request
- User impact if declined/Reason for urgency: Enterprises really need this and it missed 149 unfortunately.
- Code covered by automated testing?: no
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: medium
- Explanation of risk level: Changes some internal naming of some functions in AI controls, but has been thoroughly tested
- String changes made/needed?: Yes, but policy only.
- Is Android affected?: no
Comment 15•4 months ago
|
||
I see the string changes are policy only, but wanted to get a thumbs up from l10n team.
Comment 16•4 months ago
|
||
Hi, considering the importance and the fact that these are policy only I'm okay with this uplift.
Updated•4 months ago
|
Updated•4 months ago
|
Comment 17•4 months ago
|
||
| uplift | ||
Comment 18•4 months ago
|
||
Note: we need someone to uplift l10n-changesets.json as close as possible to the next dot release.
P.S. it would be nice to get bug 2022452 to a resolution, which would mitigate this need.
Updated•3 months ago
|
Updated•3 months ago
|
Comment 19•3 months ago
|
||
| uplift | ||
Description
•