2005-12-10 Trunk builds
Fixes:
- Fixed: 318489 - Unable to create new XMLHttpRequests from an XPCNativeWrapped window. (Some Greasemonkey scripts break, and break in a way that can be only be fixed in ways that make them more likely to have security holes.)
- Fixed: 303713 - textbox.dispatchEvent(keyEvent) no longer adds character to textbox in Firefox 1.0.6.
- Fixed: 266933 - Flash movies using a WMODE other than "windowed" will not start playing if they are not visible in the page.
- Fixed: 306538 - Autocomplete doesn't work without a mousemove event.
- Fixed: 201528 - Browser ignores MARQUEE BEHAVIOR = "SLIDE".
Trunk regressions:
- Since Dec 9: 319732 - Frequent crash while typing string to search for in page (find as you type).
- Since Sept 22: 309521 - Puzzle-piece UI for missing plugins is missing.
Trunk checkins between 2005-12-04 06:00 and 2005-12-10 06:00
December 10th, 2005 at 8:31 pm
If the Find crash annoys you, go back to a Dec 7 build, not a Dec 8 build. Dec 8 builds on all platforms had a very frequent crash at GetSelectionClosestFrameForChild, bug 319558.
December 11th, 2005 at 3:45 pm
The Find crash was fixed today, bug 319732.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051211 Firefox/1.6a1 ID:2005121105
December 11th, 2005 at 11:24 pm
Nevermind… The bug has been reopened.
December 14th, 2005 at 4:24 pm
Another attempt at a fix for 319732 just went in. Tomorrow’s builds should have the fix.
December 14th, 2005 at 4:38 pm
is this trunk actually usable? I mean the Trunk nightly builds…I heard there should be whole new concept in rendering, e.g. Gecko 1.9 should be totaly different from 1.8, and as I see it is in alpha state and it do not promise much use. Is it faster? Better? CSS3? Or what.
What are your experiences? Xavier, anyone?
And last question…last reports indicates that the next breakthrough should be Firefox 3.0, NOT 2.0, what I thought. I meant 2.0 should become this trunk, the new awaited lots of changes under the hood. But some news sites reported that 2.0 will only bring cosmetic GUI changes on 1.8branch, and that the real backend change would be Firefox 3.0.
Thanks for some useful links, hope news-sites are mistaken and we’ll get revolutionary FF20 as soon as possible, at least in beta stage.