2005-08-17 Branch builds

Fixes:

  • Fixed: 258285 - Find Toolbar sometimes appears when typing into textareas / form input fields.
  • Fixed: 303267 - Back/Forward / bfcache breaks JavaScript.
  • Fixed: 299239 - BiDi: Caret is stuck when reaching a single LTR character in RTL text.
  • Fixed: 304748 - "Bookmark This Tab" command doesn't work if the context element is the tabbar itself.
  • Fixed: 304362 - Parse W3C-DTF dates in feeds correctly.

Fixes for regressions:

  • Fixed: 299825 - Search plugins in App directory are updated into Profile directory (resulting in double Search Bar entries).
  • Fixed: 304590 - Crash [@ nsWindowSH::GetProperty] when loading a page with many frames (since ~Aug 12).
  • Fixed: 303267 - Back/Forward break JavaScript (since July 31).

Please be on the lookout for focus regressions from the fix for bug 258285. Aaron says "Focus code is notoriously touchy and I would like to verify this doesn't break anything."

Major regressions since Deer Park Alpha 2:

  • Since branching: 304608 - Automatic app update updates to trunk.
  • Since July 26: 302136 - Two clicks on "Install Now" button are necessary to install an extension. Fixed in today's builds after 10am, including the Windows nightly.

Gecko 1.8 branch checkins between 2005-08-16 07:00 and 2005-08-17 07:00

Windows builds: Windows nightly, Windows hourly (discussion)

Linux builds: Linux nightly, Linux hourly

Mac builds: Mac nightly, Mac hourly

11 Responses to “2005-08-17 Branch builds”

  1. Elder Young Says:

    Even though I thought it was the nsWindowSH::SetProperty bug that caused constant crashes when Session Saver and a few other extensions are used, it seems that Session Saver now works. Yippee!

  2. Manoj Mehta Says:

    Anyone notice how the extensions window doesn’t have a scrollbar?

  3. Manoj Mehta Says:

    Anyone notice how the extensions window doesn’t have a scrollbar in either Firefox 1.06 or the latest nightly from the branch and trunk.

  4. Elder Young Says:

    If you mean the extensions manager, mine has a scrollbar.
    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050817 Firefox/1.0+ ID:2005081711

    I unistalled 1.0.6 so I can’t comment on whether it has a scrollbar in the extensions manager.

  5. CooLynX Says:

    Still no scrollbars… :(

  6. pika unforgiven Says:

    EM scrollbar WFM on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050817 Firefox/1.0+ ID:2005081719

    normally i would use trunk builds but im stuck using branch builds thanks to this bug:
    #304874 – [Firefox]-Extensions no longer work in trunk builds [Win]

    not that it really matters that much tho, currently most “unstable” things are checked into the trunk, then checked into the branch builds once found stable, but i really like being on the “bleeding edge” when it comes to firefox….

  7. CooLynX Says:

    I’m using Opera 7.5x theme 1.1.050514 and in this theme there ar no scrollbars at all. :( Using default theme scrollbars are missing only in extensions window.

  8. Moktoipas Says:

    I tested some themes and with all of them i don’t have any scrollbar.

    But with the default theme they appears nomaly even in the extensions window.

  9. CooLynX Says:

    Sorry, there is a scrollbar in extension window using default theme! My fault. :P

  10. Manoj Mehta Says:

    I am using the default theme with a new profile and EM doesn’t have a scrollbar. I’ll nuke my installation/profile and try again.

  11. Sohail Mirza Says:

    I just noticed that Deer Park does not allow a frame’s src attribute to invoke a javascript function any longer. The simplified test case below works in Firefox 1.0.6 but not Deer Park 08-17 nightly:


    <html>
    <head>
    <script type="text/javascript">
    function fooBar() { return "Hello World"; }
    </script>
    <frameset rows="50%,50%">
    <frame name="topFrame" src="javascript:parent.fooBar();">
    <frame name="bottomFrame" src="http://www.mozilla.org">
    </frameset>
    </html>

    Is this a regression, or is calling a javascript function in a frame’s src attribute considered a XSS vulnerability?