We're now locked down for Gecko 1.8rc1 -- the first release candidate of Gecko 1.8. I'd like to urge everyone to download this (in a Camino or Seamonkey branch nightly, or in the Firefox 1.5 release candidate once that's available) and bang on it. Camino testing is especially welcome, since Camino exercises a lot of important embedding code that's not exercised by either Seamonkey or Firefox, but is used by a variety of other apps. If there are stop-ship bugs, we really need to know, and the sooner the better.
I don't really think we'll find many stop-ship issues, though. This is by far the best release candidate we've ever done. It's actually a real release candidate, unlike the previous ones!
Posted by bzbarsky at October 26, 2005 9:39 AMBoris,
Are the camino nightlies you mention the ones you can find here:
http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-1.0/
Or is it a different directory I need to be looking for?
Martijn
Posted by: Martijn on October 26, 2005 10:37 AMMartijn: That's the correct directory. Get downloading! :)
Posted by: Samuel Sidler on October 26, 2005 11:26 AMYep. That looks like the right directory.
Posted by: Boris on October 26, 2005 1:45 PMHave I told you lately that I love you(r work on Mozilla/Gecko)?
Posted by: Posted by: Klopsers on October 26, 2005 03:48 PM on October 26, 2005 1:48 PMHave been surfing with it all day, feels rock solid, Java & flash work perfectly and smooth (map24.nl).
So far I can confirm what you say about gecko 1.8 sure feels like a final to me :) Gecko 1.8 looks to be in great shape.
Posted by: Martijn on October 26, 2005 5:59 PMOne thing is weird though:
if I have multiple tabs open with a Java applet in one and I switch to another tab, the applet sometimes appears in the focused tab. Known bug?
Posted by: Martijn on October 27, 2005 3:50 AMMartijn, that's probably https://bugzilla.mozilla.org/show_bug.cgi?id=277067 (or any of the several specific plugin bugs that all should get fixed by bug 277067).
Camino used to have some hacks in place that alleviated most of the plugin-drawing-on-the-wrong-tab problems, but some recent changes on the branch made the hacks unstable, so they were ripped out. The JEP also used to work around some of the Java ones, but I think another recent change diminished the effectiveness of the JEP's work-arounds.
Posted by: Smokey Ardisson on October 27, 2005 7:18 AMAah ok thanks Smokey!
Posted by: Martijn on October 27, 2005 10:48 AMI suppose the chance of this https://bugzilla.mozilla.org/show_bug.cgi?id=309550 rendering regression getting fixed at this very late state in the release cycle tends towards zero?
Posted by: steve england on November 3, 2005 12:42 PMYeah, I think the chances of that getting fixed for 1.8 are pretty minimal at this point unless it's breaking sites... If it is, you should nominate it for blocking (and perhaps email roc and ask him to look at it?)