TBH I knew there was a good reason we developed with https on localhost, but I hadn't yet found the time to go into it to dispute this. This is one of them.
govind via monorail
unread,
Feb 10, 2021, 6:47:16 PM2/10/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
This bug requires manual review: M89's targeted beta branch promotion date has already passed, so this requires manual review Before a merge request will be considered, the following information is required to be added to this bug:
Chrome OS Only: 8. Was the change reviewed and approved by the Eng Prod Representative? See Eng Prod ownership by component: http://go/cros-engprodcomponents
Please contact the milestone owner if you have questions. Owners: benmason@(Android), bindusuvarna@(iOS), geohsu@(ChromeOS), pbommana@(Desktop)
Merge approved: your change passed merge requirements and is auto-approved for M96. Please go ahead and merge the CL to branch 4664 (refs/branch-heads/4664) manually. Please contact milestone owner if you have questions. Merge instructions: https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/process/merge_request.md Owners: govind (Android), harrysouders (iOS), dgagnon (ChromeOS), srinivassista (Desktop)
Is this flag going to removed at some point? My company currently relies on it and would like to know at which point we need to freeze our chrome upgrades.
cthomp via monorail
unread,
Jan 18, 2022, 1:10:49 PM1/18/22
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
We would like to be able to remove it, but ideally that would mean that we've addressed all of the issues folks have with plain http://localhost. If you (or anyone else active on this bug) have specific issues you're running into that requires the use of this flag, could you share them here so we can keep track of them and try to prioritize fixing them by default?
To set some expectations, I don't know when we'll have time to fix each edge case, but I don't think we'd want to get rid of this flag until we have an alternative (e.g., more settings in DevTools maybe) or plain-http-localhost has reached parity with https://localhost. Additionally, if there's a venue/mailing list that would be most helpful for announcing this change (when/if we do remove the flag), let me know -- I'd be happy to send an FYI announcement to blink-dev@ or security-dev@ for example.
ericlaw via monorail
unread,
Apr 18, 2022, 3:44:43 PM4/18/22
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Merge approved: your change passed merge requirements and is auto-approved for M102. Please go ahead and merge the CL to branch 5005 (refs/branch-heads/5005) manually. Please contact milestone owner if you have questions. Merge instructions: https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/process/merge_request.md Owners: eakpobaro (Android), harrysouders (iOS), ceb (ChromeOS), srinivassista (Desktop)