Question: HTTPS everywhere...problem

[Felipe Nascimento de Moura]

Well, I read it in the some doumentation about it and the logged error
message was informing about this.
But indeed, the ES documentation is not mandatory about it. I'm trying
contact with people from the Chrome devtools about it.
I just realized it works in Firefox on Android...is a small limitation but
is some hope!

About the local domain suggested by Mark, I will have to check the
availability to configure a dedicated DNS server there...this is also an
interesting possibility.

So, as for the ES definitions, this is not a rule to be applied in all
browsers in a near future?

Thanks.

[ ]s

*--*

*Felipe N. Moura*
Web Developer, Google Developer Expert
<https://developers.google.com/experts/people/felipe-moura>, Founder of
BrazilJS <https://braziljs.org/> and Nasc <http://nasc.io/>.

Website:  http://felipenmoura.com / http://nasc.io/
Twitter:    @felipenmoura <http://twitter.com/felipenmoura>
Facebook: http://fb.com/felipenmoura
LinkedIn: http://goo.gl/qGmq
---------------------------------
*Changing  the  world*  is the least I expect from  myself!


On Sat, Aug 4, 2018 at 7:08 PM Claude Pache <claude.pache at gmail.com> wrote:

>
> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <felipenmoura at gmail.com>
> a écrit :
>
> I know of (and I also support) the HTTPS everywhere campaign.
>
>
> I don’t think that ECMAScript has any feature related to the http
> protocol, or that make a distinction between secure and non-secure
> contexts. Wrong mailing list?
>
> —Claude
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/30215057/attachment-0001.html>