>If browser vendors aren't careful But they are being careful. This rollout has been taking place slowly over the last two years, and continues to do so. Cha

>If browser vendors aren't careful But they are being careful. This rollout has been taking place slowly over the last two years, and continues to do so. Changes are incremental to give developers a chance to adapt, and to prevent users from getting used to warnings. HTTP/2 requires https. New APIs have started requiring https. And only forms with passwords or CC inputs will trigger security warnings. These are incremental steps. I don't know why people think browser vendors haven't considered this stuff before. Eventually vendors will start deprecating existing APIs to continue the migration towards requiring https. That will put more heat on developers, but only after they've ignored warnings for literal years. But even the change announced today is only a UI update to the omnibar. It's hardly earth shattering.