Hi Zach - we don't need a new policy - we have an existing policy.  Also, the policy would now need to be pushed to all users instead of just those that change the policy since client default behavior trumps if policy is not set.  Thirdly, the server-side team doesn't use crbug - they use buganizer, so we would need to file a buganizer issue for this.  And, fourthly, we should *NOT* check-in any CL client-side to change behavior UNTIL server side is sending the correct fully filled in policy for screen lock (which it does not do now - see point #2 above).  Once that's in, the CL can be checked in client side.  That means current hopeful milestone may be missed for client side default behavior change.  I will file a server-side bug for this.

Thank you.

This bug has an owner, thus, it's been triaged. Changing status to "assigned".