[varenc]

For local development, Chrome has a flag that lets you force specific origins to be treated as secure:

  chrome://flags/#unsafely-treat-insecure-origin-as-secure

I don't think Firefox has anything equivalent though? This bug on the topic is unassigned: https://bugzilla.mozilla.org/show_bug.cgi?id=1410365

[aaronharnly]

Interesting! Though I find that behaves rather strangely – seems to clear itself on every launch.

[varenc]

Yea that's annoying, but I believe that's intentional... you can pass that flag in as an arg when you launch chrome though so you don't have to set it up each time.

[mort96]

I don't imagine that works on mobile chrome, which is what the parent comment was talking about.

[_fzslm]

It does, on Android.

[mort96]

Ah, TIL.

Though it doesn't work on iOS Chrome, and you want to test on iOS too obviously.

[Wowfunhappy]

iOS Chrome is just Safari with a Google skin, Google has no control over this type of thing.

[mort96]

That's both true and completely irrelevant.

[Wowfunhappy]

Well, it's relevant insofar as you're complaining to the wrong company.

Does this behavior even exists in iOS Chrome? If it does, it exists in Mobile Safari as well.