2005-08-12 Trunk builds
New stuff:
- Fixed: 303848 - Do a better job of integrating RSS pretty print into Firefox.
- Fixed: 285064 - Rename "Sanitize" feature to "Clear Private Data".
- Fixed: 271097 - Searchplugin auto update should ask user.
- Fixed: 304403 - Better safe mode UE.
- Fixed: 300412 - A menu option for Bookmark All Tabs and bookmark options in the right-click menu for tabs.
Fixes:
- Fixed: 259429 - Proxy: Software Update does not request authentication and fails.
- Fixed: Followup changes to 296639 (Split windows into an inner and outer object).
- Fixed: 284868 - HTTP Referer not sent at all when "saving link as...".
- Fixed: 304115 - Compreg.dat isn't rebuilt properly after Software Update.
- Fixed: 299745 - Updating Firefox window / progress bar doesn't maintain look of software update UI.
- Fixed: 255116 - Pressing Home or Shift+Home should close autocomplete.
- Fixed: 300297 - Transparent dependent xul window opened from chrome causes browser window to be redraw as transparent window in Deer Park.
Fixes for regressions:
- Fixed: 302809 - AJAX regression: POST setRequestHeader causes NS_ERROR_ILLEGAL_VALUE for invalid headers.
- Fixed: 301358 - HTTP "refresh" doesn't load page with bfcache enabled.
- Fixed: 302885 - Can't type into rich text editor, designMode not working anymore (since July 31).
- Fixed: 302281 - [Linux] Open links from external applications always opens link in new window (since July 26).
Security fixes:
- Fixed: 303181 - Security hole.
Major regressions since Deer Park Alpha 2:
- Since Aug 12: 304418 - "Save link as" broken.
- Since Aug 12: 304457 - Can't tab between location and search boxes.
- Since July 31: 303267 - Back/Forward break JavaScript.
- Since July 26: 302136 - Two clicks on "Install Now" button are necessary to install an extension.
All checkins between 2005-08-11 07:00 and 2005-08-12 07:00
August 13th, 2005 at 4:28 am
Cool- Fixing 302885 (rich text) ought to bring some loud applause.
August 14th, 2005 at 3:53 pm
Why am I not authorised to access bug 303181? Why shouldn’t I know the details of a security flaw in a browser I use?
August 14th, 2005 at 6:20 pm
Does anyone who messed with the add bookmark dialog? I could strangle that moron, they just can’t stop them selfs from screwing it up more and more…
August 14th, 2005 at 10:18 pm
homebond:
Read the Mozilla security bug policy.
In short, the bug will go public about 2 weeks (?) after a they release a milestone with the fix included, or if the bug becomes public knowledge, usually by the Full Disclosure mailing list, or by another security website, whichever comes first.