Thanks for the reply. My problem with display lists is that they only contain
this information about nodes within the viewport. I'm interested in all nodes
that take up space within the document.
I know Firefox can calculate the necessary information for nodes outside of the
viewport because I
Great stuff all around! Thank you for the update.
Nick
On Fri, Apr 15, 2016 at 4:07 AM, Jonathan Griffin wrote:
> Engineering Productivity is off to a great start in 2016; here’s what we’ve
> been up to in Q1.
> Build System
>
> Build system improvements are a major priority for Engineering Prod
Congrats! Impressive results. Thanks for your work.
On 14/04/16 20:07, Jonathan Griffin wrote:
Engineering Productivity is off to a great start in 2016; here’s what we’ve
been up to in Q1.
Build System
Build system improvements are a major priority for Engineering Productivity
in 2016. The buil
On Thu, Apr 14, 2016 at 10:54 PM, Chris Peterson
wrote:
>
> Focusing on third-party session cookies is an interesting idea.
> "Sessionizing" non-HTTPS third-party cookies would encourage ad networks
> and CDNs to use HTTPS, allowing content sites to use HTTPS without mixed
> content problems. Muc
On Fri, Apr 15, 2016 at 2:12 AM, Jason Duell wrote:
> On Thu, Apr 14, 2016 at 10:54 PM, Chris Peterson
> wrote:
>
>>
>> Focusing on third-party session cookies is an interesting idea.
>> "Sessionizing" non-HTTPS third-party cookies would encourage ad networks
>> and CDNs to use HTTPS, allowing c
Am Mittwoch, 23. September 2015 02:33:52 UTC+2 schrieb Jonas Sicking:
> On Tue, Sep 22, 2015 at 11:16 PM, Eric Rescorla wrote:
> >> The api has been extensively discussed with all browser vendors and has
> >> changed substantially in response to this
> >
> > Can you please point me to those change
This is really cool!
Though I much prefer firefoxtree's namespace updating to keep track of
remote heads over using bookmarks. I want a label that will always point
to the last known head on the server, so e.g
`hg update central && hg commit -m "Foo"` should not move 'central'.
Using bookmarks to
On Thu, Apr 14, 2016 at 10:54 PM, Chris Peterson wrote:
> Thanks for all the feedbck. I anticipated this proposal might not be
> practical with real world sites, so it's better to halt it here. :) I should
> have framed this email as an RFC instead of an intent to ship.
>
Thanks Chris for bringin
I'm working on this. From an implementation point of view, we have almost
everything done and behind pref.
There are still some patches to review but it should not take too long.
The only missing piece is to change form submission but I should be able to
finish it for the next week.
More important
I'm sure most of you have experienced the pain of long backlogs on Try
(Windows in particular). While we'd all love to have larger pools of test
machines (and our Ops people are actively working on improving that!), one
often-overlooked thing people can do to help with the backlog Right Now is
to c
I wonder if there is any use cases to do multiple Try pushes of different
changesets but with the same bug number. Should we automatically cancel the
old ones when there is a new one?
On Fri, Apr 15, 2016 at 8:47 AM, Ryan VanderMeulen <
rvandermeu...@mozilla.com> wrote:
> I'm sure most of you hav
On 15/04/16 18:09, Tim Guan-tin Chien wrote:
I wonder if there is any use cases to do multiple Try pushes of different
changesets but with the same bug number. Should we automatically cancel the
old ones when there is a new one?
Unfortunately there are legitimate uses for e.g. comparing the eff
Hello dev-platform,
TL;DR: MozAfterPaint and nsIDOMWindowUtils has been given some extra stuff
to make it easier to be sure that something you care about has been
painted. This is good, at the very least, for Talos tests.
Full-details:
I've recently made a change to MozAfterPaint that some of yo
We could also make the default behavior be to cancel old pushes. And
then enable push message syntax for opting in to not cancelling.
/ Jonas
On Fri, Apr 15, 2016 at 10:19 AM, James Graham wrote:
> On 15/04/16 18:09, Tim Guan-tin Chien wrote:
>>
>> I wonder if there is any use cases to do multip
On Fri, Apr 15, 2016 at 12:36 PM, Jonas Sicking wrote:
> We could also make the default behavior be to cancel old pushes. And
> then enable push message syntax for opting in to not cancelling.
>
>
This could be very frustrating (and cause farm work to be wasted) if it
happened accidentally.
Perh
If this is a serious problem, and I can easily believe that it is, have we
considered having a default behaviour of cancelling all unfinished Try jobs
running for a given user when they push again? Based on how I've seen
people use Try over the years, I suspect a significant majority of pushes
are
See bug 593096. (Hah! I anticipated you guys by almost 700,000 bugs!)
It's currently WONTFIX, but there's some relevant discussion in there.
On 04/15/2016 12:46 PM, Mike Connor wrote:
If this is a serious problem, and I can easily believe that it is, have we
considered having a default behaviou
On 15/04/2016 20:46, Mike Connor wrote:
For cases where a developer needs to run multiple runs at once, we can add
an override in the trychooser syntax. I think that's a corner case
It isn't when you do any kind of talos "need to fix / not regress perf"
work.
I agree with Jim that we should
On 4/15/16 1:09 PM, Tim Guan-tin Chien wrote:
I wonder if there is any use cases to do multiple Try pushes of different
changesets but with the same bug number.
A significant fraction of my try pushes are like this, actually.
Typically this happens when I do a try push of a multi-changeset que
On Thu, Apr 14, 2016 at 9:34 PM, wrote:
> When will mozilla-central use generaldelta?
>
It's complicated. But https://hg.mozilla.org/experimental/mozilla-central-gd
exists now. It is ~400 MB smaller than mozilla-central. I also filed bug
1265075 to track advertising a generaldelta bundle via the
On Thu, Apr 14, 2016 at 6:45 PM, Dave Townsend
wrote:
> On Thu, Apr 14, 2016 at 5:22 PM, Gregory Szorc wrote:
>
>> I'm pleased to announce the immediate availability of some *experimental*
>> read-only Mercurial repositories containing the combined, useful history of
>> the various Firefox repos
On Fri, Apr 15, 2016 at 01:29:10PM -0700, Gregory Szorc wrote:
On Thu, Apr 14, 2016 at 6:45 PM, Dave Townsend
wrote:
Does this mean that it contains the full history including CVS?
No. Adding a Mercurial repo with CVS history isn't on the priority list.
Make a case for it improving developer
I also often have multiple pushes going at the same time. My
suggestion to solve this problem is: have a cron job that detects
users who have more than N pushes with jobs still going, and send them
an email saying "you have a lot of jobs going, here's the list; you
might find something you should c
On Fri, Apr 15, 2016 at 7:16 AM, Andrew Halberstadt <
ahalberst...@mozilla.com> wrote:
> This is really cool!
>
> Though I much prefer firefoxtree's namespace updating to keep track of
> remote heads over using bookmarks. I want a label that will always point
> to the last known head on the server
The W3C is proposing a charter for:
Timed Text Working Group
http://w3c.github.io/charter-drafts/timed-text-charter-2016.html
https://lists.w3.org/Archives/Public/public-new-work/2016Apr/0010.html
The diff between this charter and the group's previous charter is:
http://services.w3.org
> On Apr 15, 2016, at 12:44 PM, Jim Blandy wrote:
>
> On Fri, Apr 15, 2016 at 12:36 PM, Jonas Sicking wrote:
>
>> We could also make the default behavior be to cancel old pushes. And
>> then enable push message syntax for opting in to not cancelling.
>>
>>
> This could be very frustrating (a
[ also bcc:ed David Burns, who's the proposed chair of the group ]
The W3C is proposing a charter for:
Browser Testing and Tools Working Group
http://w3c.github.io/charter-drafts/browser-testing-tools.html
https://lists.w3.org/Archives/Public/public-new-work/2016Apr/0006.html
Mozilla has t
On 2016-04-15 7:47 AM, Tantek Çelik wrote:
What steps can we take in this direction WITHOUT breaking web compat?
E.g. since one of the issues raised is that *every* time a user
enters/submits a password over HTTP (not secure), it opens them to
being sniffed etc., thus it's good to discourage th
I'm not sure there's much to say here. I think we should remain
uninterested in the TTML efforts. Work to define translation from
CEA608 and CEA708 to WebVTT is worthwhile, and I'd like to see it
supported. Unfortunately our interest in WebVTT has been mostly
theoretical recently, so I don't see us
On Fri, Apr 15, 2016 at 4:32 AM, Jip de Beer wrote:
> Thanks for the reply. My problem with display lists is that they only contain
> this information about nodes within the viewport. I'm interested in all nodes
> that take up space within the document.
>
> I know Firefox can calculate the neces
On Sat, Apr 16, 2016 at 1:47 AM, Ryan VanderMeulen <
rvandermeu...@mozilla.com> wrote:
> I'm sure most of you have experienced the pain of long backlogs on Try
> (Windows in particular). While we'd all love to have larger pools of test
> machines (and our Ops people are actively working on improvi
On 04/15/2016 05:11 PM, Xidorn Quan wrote:
On Sat, Apr 16, 2016 at 1:47 AM, Ryan VanderMeulen <
rvandermeu...@mozilla.com> wrote:
I'm sure most of you have experienced the pain of long backlogs on Try
(Windows in particular). While we'd all love to have larger pools of test
machines (and our Op
On Sat, Apr 16, 2016 at 10:24 AM, Steve Fink wrote:
> On 04/15/2016 05:11 PM, Xidorn Quan wrote:
>
>> On Sat, Apr 16, 2016 at 1:47 AM, Ryan VanderMeulen <
>> rvandermeu...@mozilla.com> wrote:
>>
>> I'm sure most of you have experienced the pain of long backlogs on Try
>>> (Windows in particular).
On Friday, April 15, 2016 at 5:11:55 PM UTC-7, Xidorn Quan wrote:
> On Sat, Apr 16, 2016 at 1:47 AM, Ryan VanderMeulen <
> rvandermeu...@mozilla.com> wrote:
>
> > I'm sure most of you have experienced the pain of long backlogs on Try
> > (Windows in particular). While we'd all love to have larger
On 04/15/2016 11:29 PM, Gregory Szorc wrote:
On Thu, Apr 14, 2016 at 6:45 PM, Dave Townsend
wrote:
On Thu, Apr 14, 2016 at 5:22 PM, Gregory Szorc wrote:
I'm pleased to announce the immediate availability of some *experimental*
read-only Mercurial repositories containing the combined, useful
On 4/15/16 7:47 AM, Tantek Çelik wrote:
What steps can we take in this direction WITHOUT breaking web compat?
Would this feature actually break web compatibility? Or just needlessly
annoy users?
In his original post, Henri argued that clearing non-HTTPS cookies
between sessions would not "B
For me, having the CVS history in the mozilla-central repo would be
much more helpful than having all the different repositories in one.
Nick
On Sat, Apr 16, 2016 at 11:41 AM, smaug wrote:
> On 04/15/2016 11:29 PM, Gregory Szorc wrote:
>>
>> On Thu, Apr 14, 2016 at 6:45 PM, Dave Townsend
>> wro
37 matches
Mail list logo
