2005-08-23 Trunk builds
The most exciting thing that has happened on the trunk since the branch point is the landing of Cairo, which will soon replace Gecko's existing graphics library, GFX. You can download an experimental build for Linux or an experimental build for Windows from shortly before the landing that uses Cairo for all graphics.
Trunk builds of Firefox use the version number 1.6a1, which prevents most existing extensions from working. You can work around this by setting app.extensions.version in about:config to 1.0+.
If you use a trunk build with your branch profile, your extensions will be disabled and you'll have to re-enable them if you return to the branch. If you want to use different profiles on the trunk and branch, you can make Firefox bring up the profile manager with "firefox.exe -p", and you can make Firefox use a specific profile with "firefox.exe -p profilename".
Fixes that will probably be trunk-only:
- Fixed: 285872 - GIF Decoder: replace gathering buffer with dynamic malloc to fixed 256 bytes hold.
- Fixed: 243486 - Lots of small document.write spend a lot of time in cache code.
- Fixed: 258864 - View > 'Full Screen' menu entry does not become ticked / checked when in full screen mode.
- Fixed: 269125 - img.onerror should fire for non-existent files.
- Fixed: 300313 - Line/word breaking service should be deCOMtaminated and simplified.
- Fixed: 32807 - Triple-clicking should select paragraph, not line.
- Fixed: 296036 - Fix event coordinate handling.
Fixes that are likely to be checked into the branch too:
- Fixed: 277434 - Setting .type property on <object> element doesn't create an HTML attribute type.
- Fixed: 305448 - Leaving document while script loaded via document.write is loading leaks the world.
- Fixed: 305236 - The bfcache stores too many things in the cache.
- Fixed: 304882 - Bookmarklet fails (accessing location.href after document.write()).
- Fixed: 189308 - JavaScript <body onscroll> event don't work with mouse scroll, mouse wheel or keyboard arrow.
- Fixed: 302433 - Helper application temp files litter the desktop on Mac.
I'm not keeping track of day-to-day regressions on the trunk.
Trunk checkins between the branch point (around 2005-08-12 01:00) and 2005-08-23 07:00
August 23rd, 2005 at 11:24 pm
http://wiki.mozilla.org/FutureGfxWhiteboard has information about the plan for Cairo to replace GFX.
August 23rd, 2005 at 11:39 pm
I set the pref app.extensions.version as suggested, and now my extensions no longer say they are incompatible, but they remain disabled and don’t respond to the Enable command in the contextual menu. Any suggestions?
August 23rd, 2005 at 11:41 pm
Oops, is this a trunk-only tip? I’m running a branch build.
August 24th, 2005 at 12:05 am
Haha, I clearly don’t know what I’m talking about. It is a trunk build I’m using.
August 24th, 2005 at 12:35 am
The patch for bug 302433 has an approval1.8b4? request, and Boris commented “I think I’d like to do this for 1.8 to at least give users some choice here…”, so you might want to move it to the second list (unless you know something that I don’t).
August 24th, 2005 at 1:39 am
Thanks for this and the recent frequent updates; I’m sure many here are pleasantly surprised by the increased activity. :-)
August 24th, 2005 at 1:48 am
Thanks Uri, I missed that because I only skimmed the most recent comments on each bug.
August 24th, 2005 at 2:17 am
Welcome to Cairo
If you’ve been following the development of Firefox as closely as I have, you probably know exactly what Cairo is, but I’ll introduce it anyway!
An introduction
Cairo is a high quality vector based graphics system that can be used to …
August 24th, 2005 at 7:20 am
I don’t have have “app.extensions.version” — I do have “extensions.lastappversion” — is that the same setting?
It showed up as “1.0+” as a user option, though I’d never set it; only alternative seems to be to have it blank by default. Can that be right?
OSX build Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050823 Firefox/1.0+ (which won’t load extensions — “install 2.0” counts down but fails to install)
.
August 24th, 2005 at 8:36 am
in order to get extensions to work for trunk builds you must edit install.rdf to have maxversion set to 1.6a1 or 1.6+, otherwise they will not work. to do this, open the .xpi file in winzip (or any other file unzip utility), open install.rdf in a text editor and edit the value, then replace the file. this way has worked just fine for me ever since they changed it, as trunk builds ignore extensions.lastappversion changes for some reason.
oh yeah, trunk builds are currently partially broken, i dont recommend using it for a bit. i heard branch builds are kinda broken too but i havent tested for myself to find out.
August 24th, 2005 at 11:54 am
#305694 [Firefox]-dragging extension from finder produces infinite “install now” loop [Mac]
August 24th, 2005 at 12:55 pm
You have to create app.extensions.version as a new string pref because it doesn’t have a default value any more.
August 24th, 2005 at 2:45 pm
Hank, read Extensions in Deer Park…
August 24th, 2005 at 5:06 pm
No regressions?
Branch! Branch! Branch! Branch! Branch! Branch! Branch!
August 24th, 2005 at 10:22 pm
Thanks Jesse and Rowan.
Some of us with OSX can’t install extensions anyhow, until there’s a fix for bug 305694. (Others can, go figure…)
One of the knowledgeable posters in the Mozillazine thread explained that 305694 is unrelated to the version number problem, has been figured out, and is being worked on.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050824 Firefox/1.0+
August 24th, 2005 at 11:02 pm
I just downloaded the nightly from the 24th and this build has a lot of bugs. In particular, the Back and Prev buttons don’t work and the Address Bar doesn’t get updated when you click on a link. The location bar address changes when you open a new tab but now the new tab’s address is wrong.
September 15th, 2005 at 11:50 pm
[…] There have been hundreds of checkins since the previous Burning Edge trunk post. Here are some of the most exciting fixes and new features. […]