As was mentioned in passing in a couple of places, we are adding a third alpha to pick up a few things that missed the A2 cutoff. Most notable/important are the new SafeBrowsing feature and DOMStorage. This is going to a _very_ short cycle, aiming at a ship date of May 25th. (Yes, that's two weeks from now, and yes, this should be very hittable.) We need to mitigate risk wherever possible in order to stay on schedule, so we would like module owners to be very conservative about approving branch patches in the next two weeks.
Key dates for this cycle:
Friday, May 12th: Alpha 2 released, MOZILLA_1_8_BRANCH re-opens for business Tuesday, May 16th: Deadline for landing ECC cipher support Thursday, May 18th: Deadline for landing SafeBrowsing (will land on a closed tree) Monday, May 22nd: Deadline for landing DOMStorage (will land on a closed tree) Tuesday, May 23rd: Branch enters lockdown for Alpha 3 at 11:59pm PDT Thursday, May 25th: Hard freeze at noon PDT for respins as need, QA will do full smoketest runs Friday, May 26th: Alpha 3 ships
On 12-May-06, at 8:27 AM, supernov...@gmail.com wrote:
> How about tab overflow and undo closed tab?
Those are both still targeted for b1, but if they're ready in time, we will be opportunistic about taking those changes. Dietrich and I, and a lot of others, are heading to Amsterdam for XTech tomorrow, and won't be spending a lot of time hacking during that time, so we are not going to block on those additions.
On 5/12/06, Mike Connor <mcon...@mozilla.com> wrote:
> Friday, May 12th: Alpha 2 released, MOZILLA_1_8_BRANCH re-opens for > business
So should the tree be re-opened now? Or do we want to keep it closed as we merge back the things landed on the 1.8 branch when trunk was closed, and *then* open it?
cheers, mike -- / mike beltzner / user experience lead / mozilla corporation /
Search Suggest is nice, but what about an option to switch to Search History (default behavior in Firefox 1.x)? And an option in Tabs options "Show close button on each tab" enabled by default. Disabled will show close button on the right, just like in Firefox 1.x
A pref to have close buttons tabs revert to the right hand close button has been won't fixed https://bugzilla.mozilla.org/show_bug.cgi?id=324227 [Implement old tab close button as a preffable option.]. I doubt your other issue will get a pref either. There may be a search plugin that does not use the search suggest that you can install.
Kevin Brosnan
On 14 May 2006 14:15:04 -0700, kalphegor <kalphe...@gmail.com> wrote:
> Search Suggest is nice, but what about an option to switch to Search > History (default behavior in Firefox 1.x)? > And an option in Tabs options "Show close button on each tab" enabled > by default. Disabled will show close button on the right, just like in > Firefox 1.x
> And an option in Tabs options "Show close button on each tab" enabled > by default. Disabled will show close button on the right, just like in > Firefox 1.x
As Kevin Brosnan said, this was rejected. There was some discussion in dev.apps.firefox about making it a pref based on feedback, but that didn't seem to lead to anything.
Speaking of dev.apps.firefox, this probably belongs there if there's any more discussion. :)
I'd like to talk to someone at Mozilla and you're the right developer to help us. Could you?
Please, I've missed Pluck Firefox Edition Sidebar. Pluck Sidebar works very well on Internet Explorer but not on Firefox. Why? Could you please make it work there too? I've taken FX 1.5 out and installed Bon Echo but now no Pluck Sidebar could be installed unfortunately. Pluck is just fine (www.pluck.com). And you're just a developer who could make it real.
> As was mentioned in passing in a couple of places, we are adding a > third alpha to pick up a few things that missed the A2 cutoff. Most > notable/important are the new SafeBrowsing feature and DOMStorage. > This is going to a _very_ short cycle, aiming at a ship date of May > 25th. (Yes, that's two weeks from now, and yes, this should be very > hittable.) We need to mitigate risk wherever possible in order to > stay on schedule, so we would like module owners to be very > conservative about approving branch patches in the next two weeks.
> Key dates for this cycle:
> Friday, May 12th: Alpha 2 released, MOZILLA_1_8_BRANCH re-opens for > business > Tuesday, May 16th: Deadline for landing ECC cipher support > Thursday, May 18th: Deadline for landing SafeBrowsing (will land on a > closed tree) > Monday, May 22nd: Deadline for landing DOMStorage (will land on a > closed tree) > Tuesday, May 23rd: Branch enters lockdown for Alpha 3 at 11:59pm PDT > Thursday, May 25th: Hard freeze at noon PDT for respins as need, QA > will do full smoketest runs > Friday, May 26th: Alpha 3 ships
Well if we're talking extension absorbtion I would definately like to see the stop/refresh ext made official. It melds together the stop and refresh buttons to give the same functionality but with one button.
Mike Connor wrote: > On 12-May-06, at 8:27 AM, supernov...@gmail.com wrote:
> > How about tab overflow and undo closed tab?
> Those are both still targeted for b1, but if they're ready in time, > we will be opportunistic about taking those changes. Dietrich and I, > and a lot of others, are heading to Amsterdam for XTech tomorrow, and > won't be spending a lot of time hacking during that time, so we are > not going to block on those additions.
richard_pe...@yahoo.co.uk wrote: > Well if we're talking extension absorbtion I would definately like to > see the stop/refresh ext made official. It melds together the stop and > refresh buttons to give the same functionality but with one button.
As I recall the plan is to do that, as part of the UI overhaul.
Robert Accettura wrote: > richard_pe...@yahoo.co.uk wrote: >> Well if we're talking extension absorbtion I would definately like to >> see the stop/refresh ext made official. It melds together the stop and >> refresh buttons to give the same functionality but with one button. > As I recall the plan is to do that, as part of the UI overhaul.
> -R
Not exactly. As far as I can recall, it was decided that, if anything, a Go/Refresh would be a better option.
Adam Kowalczyk wrote: > Robert Accettura wrote: >> richard_pe...@yahoo.co.uk wrote: >>> Well if we're talking extension absorbtion I would definately like to >>> see the stop/refresh ext made official. It melds together the stop and >>> refresh buttons to give the same functionality but with one button. >> As I recall the plan is to do that, as part of the UI overhaul.
>> -R
> Not exactly. As far as I can recall, it was decided that, if anything, a > Go/Refresh would be a better option.
> - Adam
Do you have a link? I'd like to look into that, because I think there could be improvement in that area, but if that's the only change being made it'll be annoying to me as I use the two for different purposes.
