On 5/23/13 8:45 AM, Tim Taubert wrote:
> I talked to Gavin yesterday and we think the best approach would be to
> back out the Session Restore changes for now as they don't provide a
> real benefit other than code cleanup (and don't block any other work).
>
> The plan would then be to re-land them
On 2013-05-23 2:45 AM, Tim Taubert wrote:
I talked to Gavin yesterday and we think the best approach would be to
back out the Session Restore changes for now as they don't provide a
real benefit other than code cleanup (and don't block any other work).
The plan would then be to re-land them *wit
I talked to Gavin yesterday and we think the best approach would be to
back out the Session Restore changes for now as they don't provide a
real benefit other than code cleanup (and don't block any other work).
The plan would then be to re-land them *with* a kill switch in the same
cycle that brin
Opening Bug 874817 to add that kill switch.
Just for clarification: we might kill add-ons that specifically look at
the contents of undocumented private data structures. The advance
warning is here because we know that some such add-ons exist.
Given that all these refactorings take place on a sin
On May 22, 2013, at 5:33 AM, David Rajchenbach-Teller wrote:
> Unfortunately, we do not.
>
> For the current batch of clean-up changes, it is certainly possible to
> add a kill switch. Time-consuming, certainly not nice (the kill switch
> will creep in in dozens of places in the code, if not hund
Unfortunately, we do not.
For the current batch of clean-up changes, it is certainly possible to
add a kill switch. Time-consuming, certainly not nice (the kill switch
will creep in in dozens of places in the code, if not hundreds), but
possible.
For the upcoming set of rewrite-half-of-the-code c
On 2013-05-21 9:07 AM, David Rajchenbach-Teller wrote:
As part of project Async, we have been working on refactoring Firefox’
Session Restore to ensure that it does not block the main thread. Part
of the work has been cleaning up the code and the data structures
involved in Session Restore both t
On 5/21/13 10:01 AM, Lawrence Mandel wrote:
> cc Jorge Villalobos.
>
> - Original Message -
>> As part of project Async, we have been working on refactoring
>> Firefox’
>> Session Restore to ensure that it does not block the main thread.
>> Part
>> of the work has been cleaning up the code
cc Jorge Villalobos.
- Original Message -
> As part of project Async, we have been working on refactoring
> Firefox’
> Session Restore to ensure that it does not block the main thread.
> Part
> of the work has been cleaning up the code and the data structures
> involved in Session Restore
On Tue, May 21, 2013 at 9:07 PM, David Rajchenbach-Teller <
dtel...@mozilla.com> wrote:
> As part of project Async, we have been working on refactoring Firefox’
> Session Restore to ensure that it does not block the main thread. Part
> of the work has been cleaning up the code and the data structu
As part of project Async, we have been working on refactoring Firefox’
Session Restore to ensure that it does not block the main thread. Part
of the work has been cleaning up the code and the data structures
involved in Session Restore both to give us some maneuverability and to
improve the chances
11 matches
Mail list logo
