On Monday 2019-10-21 16:01 -0500, Mike Taylor wrote:
> Hi David,
>
> On 10/21/19 7:22 AM, L. David Baron wrote:
> > (That we haven't applied the policy that much because we've granted
> > exceptions because other browsers have shipped the features reduces
> > the effectiveness of the policy and it
Hi David,
On 10/21/19 7:22 AM, L. David Baron wrote:
(That we haven't applied the policy that much because we've granted
exceptions because other browsers have shipped the features reduces
the effectiveness of the policy and its ability to meet its goals.
This is the sort of policy that is most
Catching up on this thread after being on vacation, so I'd like to
reply to a few points.
I think the intent of the policy about exposing new features only to
secure contexts is that it should apply to CSS features. The
purpose of the policy is to push web developers towards secure
transports bec
Hello,
Here's the list of new issues found and filed by the Desktop Release QA
team in the last 7 days.
Additional details on the team's priorities last week, as well as the
plans for the current week are available at: https://tinyurl.com/y64js7do.
Bugs logged by Desktop Release QA in the last
Hi everyone,
anything that lands on integration trees (inbound or autoland) from now on
will be after the cutoff for 71, so consider the soft freeze lifted.
Thanks,
Julien
On Mon, Oct 14, 2019 at 1:02 PM Pascal Chevrel wrote:
> Hi all,
>
> We will be merging Firefox 71 from mozilla-central to
5 matches
Mail list logo