« 2005-08-10 Trunk builds
Gecko 1.8 branch created »

2005-08-11 Trunk builds

New stuff:

  • Fixed: 78510 - Link should become :visited color if URL is loaded in another window/tab/frame.

Fixes:

  • Fixed: 296464 - Crash when setting textbox value from ondragdrop handler.
  • Fixed: 266368 - Find bar is disabled when closed with "match case" focused.

Fixes for regressions:

  • Fixed: 302290 - WindowStateHolder never Release()s its timeouts.

Major regressions since Deer Park Alpha 2:

  • Since July 31: 303267 - Back/Forward break JavaScript.
  • Since July 31: 302885 - Can't type into rich text editor, designMode not working anymore.
  • Since July 26: 302281 - [Linux] Open links from external applications always opens link in new window.
  • Since July 26: 302136 - Two clicks on "Install Now" button are necessary to install an extension.

All checkins between 2005-08-10 07:00 and 2005-08-11 07:00

Windows builds: Windows nightly, Windows hourly (discussion)

Linux builds: Linux nightly, Linux hourly

Mac builds: Mac nightly (still trunk despite directory name because the 1.8 branch has not branched yet), Mac hourly

This entry was posted on Thursday, August 11th, 2005 at 12:15 pm and is filed under Trunk. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

11 Responses to “2005-08-11 Trunk builds”

  1. Tim Says:
    August 11th, 2005 at 12:42 pm

    The link marking item is quite exciting. Had just been thinking about how that would be handy a week or two ago and here it is. The firefox team, always knowing my wants before I do…

  2. Simplex Says:
    August 11th, 2005 at 1:31 pm

    I love it when bugs like 78510 are fixed. You can tell the really good ones by their bug numbers bing

  3. Simplex Says:
    August 11th, 2005 at 1:33 pm

    Ok, it ate my comment at the < sign.

    I love it when bugs like 78510 are fixed. You can tell the really good ones by their bug numbers being < 6 digits long. That means it’s been an open issue for a long time, but people still wanted to get it fixed. Usually these bugs are technically challenging.

    Here’s to hoping that the “2%-3%” decrease in speed isn’t noticeable.

  4. rotator Says:
    August 11th, 2005 at 1:50 pm

    says “apparently it’s about 3% for Seamonky Linux, 1-2% for Camino and nothing much anywhere else”, so it’s not near as bad as 2-3% across the board.

  5. Elder Young Says:
    August 11th, 2005 at 2:14 pm

    I just noticed that my cursor flickers as I move my mouse over some of my bookmarks. Instead of the selection being solid dark blue when the mouse is over a bookmark, it flickers. It only does this on some of the bookmarks though. I had this happen a few weeks ago with a build, then it was gone and now it seems to be back again.

    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050811

  6. Jean-Marc Gillet Says:
    August 11th, 2005 at 10:34 pm

    As José Jeria already told, thanks for your regular reports, easy to read and containing only the important bugs.

  7. Artem Tashkinov Says:
    August 12th, 2005 at 12:14 am

    What’s a status of bug number “303267 – Back/Forward break JavaScript”? I simply can’t work with FF until this bug get fixed.

  8. Jean-Marc Gillet Says:
    August 12th, 2005 at 12:48 am

    Artem, reading the bug report, there’s a patch ready so you’ll just need some days of patience. Until then, just disable BF cache : browser.sessionhistory.max_viewers=0 in about:config .

  9. Smokey Ardisson Says:
    August 12th, 2005 at 12:56 am

    I just noticed that the “previous” and “next” post links here are stacked on top of each other on the left side of the “article” column, rather than, say, all on one line, centered, or all on one line, “previous” on the left and “next” on the right. I don’t think they used to be like that; did you change something, or is this a regression? Camino 20050811 and DeerPark 20050810.

  10. quality Says:
    August 12th, 2005 at 7:17 am

    OT, but since Asa keeps deleting me from his blog, this is just to publicize.

    I asked a very simple question in an Ask Asa: Who was responsible for the testing/QA failure that led to a security regression in 1.0.4, how will they be censured, and what is being done to prevent a similar recurrence.

    He didn’t answer and has deleted every comment I post, in which I’ve said the same thing. I think it’s a fair question. Not answering is pretty crappy, but censoring just because he spends too much time being ‘visible’ and not enough time actually doing QA is truly pathetic.

    Asa isn’t the funloving guy his blog projects, he can be a complete idiot too. Spread the word.

  11. pika unforgiven Says:
    August 12th, 2005 at 8:12 am

    Asa isn’t the funloving guy his blog projects, he can be a complete idiot too.

    yep, quite a few have noticed that, i just learned to put up with it. seems every open-source project has their village idiots, and asa happens to be one of mozilla’s.

    back on topic, im hoping bug 302136 gets fixed soon, its become rather annoying even though i dont install new extensions all that often.