Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

godoy (2167)

  (email not shown publicly)
AOL IM: godoy0 (Add Buddy, Send Message)
Yahoo! ID: jgodoyf (Add User, Send Message)

Never doubt how stupid people can be.

Journal of godoy (2167)

Monday August 12, 2002
08:38 PM

Mozilla / Galeon / Netscape / ... bug

[ #7064 ]

It annoys me a lot.

I'm trying to edit the URL field and can't do that. There's this $#$@#"!@# bug in something basic at Mozilla's (Netscape's) code that makes the program gets lost.

Some tricks were minimizing the windows, changing tabs, double clicking the title bar, etc. but none of them worked.

The solution? Close the program and start it again.

It sux.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I've been using the mozilla nightly build since around M17 and I too saw that bug. It annoyed me quite a bit.

    I haven't seen it in recent months, but I couldn't tell you if it was a problem with my profile (which I've re-constructed a few times in the course of checking on bugs) or just a bug which has since been fixed.

    There are a number of "mozilla bugs" which are actually artifacts of old long-fixed bugs. The old bug caused some irregularity in an rdf or other profile file, and then the old bug gets fixed, but the browser is still reading in the garbage profile after you update your browser. So, you get buggy behavior.

    If using the nightly builds is an option for you, I'd grab one and re-build your profile. The problem should vanish. It's a major pain to re-build a profile, so you'd have to decide whether it's worth the effort for you. If you don't like nightly builds, you might want to wait for 1.1 which is supposed to be out in the next couple of weeks.

    Another alternative would be to back up your profile, find a set of circumstances which always shows the bug, then relauch mozilla with a file missing from your profile each time. See which file you can remove to get the bug to go away. Then start figuring out which part of that file is foobar. Then if you're feeling *real* ambitious (and looking to kill some serious time), start figuring out how to get mozilla to gracefully work around (and fix) profiles with that sort of glitch.

  • Another solution I've just found out is clicking into an xterm (probably any other application) and then typing something (and deleting it, if you want) then coming back to Mozilla/Galeon/etc.

    It's much better than closing everything.
    -- Godoy.