I have two extra suggestions for added security benefits:
1. In order to ensure that clients that support CSP will never attempt
to contact the HTTP version of the site for fetching any subresources
that may still point to http:, please make sure to serve the
|Content-Security-Policy:
We had a good conversation with Ramin last week in Tokyo. The topic of
interoperability was discussed at length, and we also talked about where
Mozilla's 2017 priorities align with KDDI's.
To summarize, Mozilla is prioritizing the Web-compatibility and Performance
of the interoperable subset of
Three quick notes about updates for things we're doing with ESlint and
Firefox:
1. There's a new help page on devmo with ESLint tips & advice:
https://developer.mozilla.org/docs/ESLint
2. Jared has been posting about about rules being enabled on his blog:
https://msujaws.wordpress.com/
3.
Has there been any feedback from Google, Apple or Microsoft?
We've landed stuff preffed off before and had to remove it in the end as it's
just so much dead weight without any chance of being preffed on. Unless there's
an intent to implement this soon from other vendors we really shouldn't put
4 matches
Mail list logo
