This data also smells weird to me. 8% of pages using basic auth seems very
very high, and only 0.7% of basic auth being done unencypted seems low.
Perhaps we should chat in London (ideally with Honza Bambas) and make sure
we're getting the telemetry right here.
Jason
On Fri, Jun 10, 2016 at
On Friday, June 10, 2016 at 10:37:04 AM UTC-7, Gijs Kruitbosch wrote:
> This async-ness will not be acceptable in all circumstances. As a
> somewhat random example: how would we localize the 'slow script' dialog,
> for which we have to pause script and then show the dialog?
Agree, there are
On 06/10/2016 12:49 PM, Gijs Kruitbosch wrote:
On 10/06/2016 09:51, zbranie...@mozilla.com wrote:
While working on the new localization API (See Intent to Implement
post from yesterday), we're developing bindings into UI languages
used by Firefox and we have some decisions to make that could be
Hi Gijs,
On Friday, June 10, 2016 at 2:49:16 AM UTC-7, Gijs Kruitbosch wrote:
> Mutation observers or mutation events? How do you decide which elements
> you observe? Observing the entire DOM tree seems like it'd likely be
> terrible for performance once we start mutating the DOM. Have you
On 4/18/16 09:59, Richard Barnes wrote:
Could we just disable HTTP auth for connections not protected with TLS? At
least Basic auth is manifestly insecure over an insecure transport. I
don't have any usage statistics, but I suspect it's pretty low compared to
form-based auth.
As a follow up
On 10/06/2016 17:26, smalolep...@mozilla.com wrote:
These are all valid concerns. The API is async by design, which allow us to
also do runtime fallback on missing or broken translations.
document.l10n.get('main').formatValue('hello', { user: '…' }).then(hello =>
…);
This async-ness
If you had any absolute paths in editor configuration, you'll need to
update them to point to 'tools/lint/eslint'.
This change was in preparation for getting |mach eslint| integrated with
the mozlint library, see bug 1258341 for details. My aim will be to
maintain backwards compatibility both in
Thanks for a lot of great feedback, Gijs!
W dniu piątek, 10 czerwca 2016 11:49:16 UTC+2 użytkownik Gijs Kruitbosch
napisał:
> Mutation observers or mutation events? How do you decide which elements
> you observe? Observing the entire DOM tree seems like it'd likely be
> terrible for
On 2016-06-10 4:51 AM, zbranie...@mozilla.com wrote:
While working on the new localization API (See Intent to Implement post from
yesterday), we're developing bindings into UI languages used by Firefox and we
have some decisions to make that could be better answered by this group.
The general
Are we still concerned about compatibility issues caused by this?
Regards,
Florin.
-Original Message-
From: dev-platform
[mailto:dev-platform-bounces+florin.mezei=softvisioninc...@lists.mozilla.org
] On Behalf Of Boris Zbarsky
Sent: Monday, June 06, 2016 11:30 PM
To:
On 6/9/16 8:53 AM, Philip Chee wrote:
> On 08/06/2016 22:59, Brian Grinstead wrote:
>
>>> The code isn't used at all in Firefox, as discussed in
>>> https://groups.google.com/forum/#!topic/mozilla.dev.developer-tools/XYPqQ58ndX4/discussion.
>>> It’s also now possible to migrate usages to the
On 10/06/2016 09:51, zbranie...@mozilla.com wrote:
While working on the new localization API (See Intent to Implement
post from yesterday), we're developing bindings into UI languages
used by Firefox and we have some decisions to make that could be
better answered by this group.
The general API
While working on the new localization API (See Intent to Implement post from
yesterday), we're developing bindings into UI languages used by Firefox and we
have some decisions to make that could be better answered by this group.
The general API is declarative and DOM-based. Instead of forcing
13 matches
Mail list logo
