Re: Issue 360956941: Flag expired : allow-insecure-localhost is expired in M130

[حسوني الحبيب‎]

في الثلاثاء، ١٣ يناير ٢٠٢٦, ١٠:٠٤ م <buganize...@google.com> كتب:

Replying to this email means your email address will be shared with the team that works on this product.

https://issues.chromium.org/issues/360956941

Changed

ch...@chops-service-accounts.iam.gserviceaccount.com added comment #14:
This flag has been marked as expiring in M130 or earlier. This bug has been opened for the Eng teams to clean up the references for the flag in the //chrome/browser/flag-metadata.json as well as references to that flag.

This is a friendly reminder to help get this clean up completed.

If you think this flag needs to be extended beyond this milestone, please follow these steps:
- If you see a flag listed as expiring that you want to keep, create a CL updating //chrome/browser/flag-metadata.json with an appropriate new expiration milestone.
- If you do this before the M130 branch you're all set; if you do it after the M130 branch you'll need to merge that CL to the M130 branch as well.

You can check the branch date for this milestone at https://chromiumdash.appspot.com/schedule
_______________________________

Reference Info: 360956941 Flag expired : allow-insecure-localhost is expired in M130

component:  Public Trackers > 1362134 > Chromium > Internals > Flags > FlagExpiryNotification
status:  Assigned
reporter:  ch...@chops-service-accounts.iam.gserviceaccount.com
assignee:  ct...@chromium.org
cc:  ct...@chromium.org, se...@chromium.org
type:  Bug
access level:  Default access
priority:  P2
severity:  S2
hotlist:  Flags-Deprecation
retention:  Component default
Component Ancestor Tags:  Internals, Internals>Flags, Internals>Flags>FlagExpiryNotification
Component Tags:  Internals>Flags>FlagExpiryNotification


Generated by Google IssueTracker notification system.

You're receiving this email because you have the following role(s) on the issue: cc (via securi...@chromium.org)
Unsubscribe from this issue.