The Official Win32 20090910 Trunk build is out.

[Peter(6)]

Nightly TRUNK thread RSS feed (courtesy DaCypher)

The Official Win32 20090910 Trunk build is out.

Previous Trunk nightly 20090909

Hourly Trunk builds (Minefield 3.7 ...): mozilla-central-linux || mozilla-central-macosx || mozilla-central-win32 || Firefox Tinderbox || Trunk Changelog
Hourly archive for Windows, Mac and Linux (not the final format yet)

Last update: 2009-09-10 -- 06:40 PDT = 13:40 UTC
Last Changeset: ecb355c31e14

Fixed:

1. #310738 [Firefox:General]-Don't show progress indicators when using bfcache to go to another page (causes slowdown) [All]
2. #417929 [Core:Disability Access APIs]-nsIAccessiblTable selectRows does not unselect previously selected rows [All]
3. #501095 [Toolkit:Preferences]-Clean up appPicker's use of XUL [Win]
4. #503627 [Core:Print Preview]-Exiting Page Setup causes broken Print Preview [Lin]
5. #504034 [Core:Graphics]-RgnRectMemoryAllocator fails thread-safety assertions even when used only on non-main thread [All]
6. #507623 [Firefox:General]-initializeSanitizer() can fail because "gPrefService.getBranch is not a function" [All]
7. #511883 [Core:Layout]-window.print() doesn't work from inside a frame [Win]
8. #513392 [Toolkit:Add-ons Manager]-Use styles on the normal icon rather than a separate hardcoded image for plugin icons [All]

Partial Landings/WIPs/Incoming:

1. #454518 [Firefox:Menus]-allow opening URLs that are not linked from the context menu (if selected) [All]
2. #490267 [Core:Graphics]-implement pref font and system font fallback for gfxFT2Fonts [Win]
   
   
3. #491201 [Core:DOM: Mozilla Extensions]-It would be useful if XMLHttpRequest.send could take the data from nsIDOMFile parameter [All]
4. #510035 [Core:Plug-ins]-Java applet does not load on Mac OS X in anything built on 1.9.2 branch and up (e.g FF 3.6 and up) [Mac]
5. #514751 [Firefox:Session Restore]-malformed URI exception during session restore [All]

Regressions/Annoying/Common bugs:

1. #423126 [Firefox:Places]-favicons aren't backed up to *.json [All]
2. #482919 [Core:HTML: Parser]-[HTML5] Add speculative parsing to the HTML5 parser [All]
3. #504797 [Core:JavaScript Engine]-Unresponsive script warning on Google Docs with jit enabled [All]
4. #505516 [Core:JavaScript Engine]-JS error on Google Docs (spreadsheets) with jit enabled [All]

Trunk fixes since 20090813 (mozilla 1.9.3) = ~ 318

[El Pino]

Going on about this tabbing changes discussed in previous post; the reasoning is very inconsistent. I think everyone agrees that no matter what system is chosen, it should be done in a consistent manner.
First they implement opening tabs relative to the parent, because then they are combined in the same spot. Then it is suggested to close them in the same manner and the argument used against it is "It's hard for people to remember where tabs came from, and so having the close operation jump unexpectedly between tabs on the tabstrip will likely be quite surprising and unpredictable". If it is hard to remember where tabs come from, then what the hell is the point in opening similar tabs next to their parent??

[WildcatRay]

Going on about this tabbing changes discussed in previous post; the reasoning is very inconsistent. I think everyone agrees that no matter what system is chosen, it should be done in a consistent manner.
First they implement opening tabs relative to the parent, because then they are combined in the same spot. Then it is suggested to close them in the same manner and the argument used against it is "It's hard for people to remember where tabs came from, and so having the close operation jump unexpectedly between tabs on the tabstrip will likely be quite surprising and unpredictable". If it is hard to remember where tabs come from, then what the hell is the point in opening similar tabs next to their parent??

You don't say?

[cuz84d]

Going on about this tabbing changes discussed in previous post; the reasoning is very inconsistent. I think everyone agrees that no matter what system is chosen, it should be done in a consistent manner.
First they implement opening tabs relative to the parent, because then they are combined in the same spot. Then it is suggested to close them in the same manner and the argument used against it is "It's hard for people to remember where tabs came from, and so having the close operation jump unexpectedly between tabs on the tabstrip will likely be quite surprising and unpredictable". If it is hard to remember where tabs come from, then what the hell is the point in opening similar tabs next to their parent??

You don't say?

That argument was valid before we started adding fun tab browsing behaviors.. now if they all closed to the left under all circumstances, that would fix it up to be consistent again.

[KennS]

El Pino, I agree with you, their argument against going back to the originating tab makes no sense what so ever.

I guess in their mind it is sort of like taking your keys out of your pocket, putting them back in your pocket and then wondering what your hand is doing in your pocket.

IMHO, it only makes sense that when I close a tab that originated from another tab, that I should go back to that originating tab. Afterall, it is where I started from, isn't it?

[cuz84d]

El Pino, I agree with you, their argument against going back to the originating tab makes no sense what so ever.

I guess in their mind it is sort of like taking your keys out of your pocket, putting them back in your pocket and then wondering what your hand is doing in your pocket.

IMHO, it only makes sense that when I close a tab that originated from another tab, that I should go back to that originating tab. Afterall, it is where I started from, isn't it?

I think what I read from that statement, is closing tab 4 and going back to say tab 2 is unexpected, but all we're asking for is going from tab 4, to tab 3, to tab 2, back toward its parent.

[brassen]

What's wrong about giving options and letting the users choose the way they prefer?

[WildcatRay]

I have put this together:

What the browser does now:

(Focused/current/parent tab IDed by following space)

A BC
A 123BC (Open tabs 1, 2, & 3 from A)
A1 23BC (Focus on tab 1)
A2 3BC (Close tab 1, focus to tab 2)
A3 BC (Close tab 2, focus to tab 3)
AB C (Close tab 3, focus to tab B)*

Where IE8 and Chrome differ and what Bug 514796 was to address:

* A BC (Close tab 3, focus to tab A)

EDIT: IE8 goes as far as coloring tabs A, 1, 2, & 3 differently from B & C.

[supernova_00]

I have put this together:

What the browser does now:

(Focused/current/parent tab IDed by following space)

A BC
A 123BC (Open tabs 1, 2, & 3 from A)
A1 23BC (Focus on tab 1)
A2 3BC (Close tab 1, focus to tab 2)
A3 BC (Close tab 2, focus to tab 3)
AB C (Close tab 3, focus to tab B)*

Where IE8 and Chrome differ and what Bug 514796 was to address:

* A BC (Close tab 3, focus to tab A)

And if you have the tabs "1" "2" and "3" as the child tabs of tab B, closing tab B would then switch to C

[WildcatRay]

Yes, that is correct.

[hhh]

What's wrong about giving options and letting the users choose the way they prefer?

The developers have a history of not wanting to add more user prefs.

[WildcatRay]

What's wrong about giving options and letting the users choose the way they prefer?

The developers have a history of not wanting to add more user prefs.

Pretty ironic for a browser that is (supposed to be?) about user customization.

[cuz84d]

Just like bug https://bugzilla.mozilla.org/show_bug.cgi?id=269664 was in FF, and now its not, not even labeled as a regression, its status hasn't been updated, nor are the UI guys on the bugmail. But if it were fixed, it would give organizations a consistent user experience when opening a new browser window or new tab.

Which is what we're all trying to get.. consistent.. not to mention printing which has plenty of bugs too.. and its inconsistent enough to stop organizations from using firefox.

[Ria]

What's wrong about giving options and letting the users choose the way they prefer?

The developers have a history of not wanting to add more user prefs.

That was Ben Goodger. A request for new pref was always a painful battle with real winners and losers. Things have changed since then.

[cuz84d]

Using the latest 12 hr trunk, Firefox feels pretty snappy..