Slashdot Mirror

Try the Mork database!!!!!!!!1!!!1!!11!eleven!!!!11!1two

There is an add-on to Firefox called SQLite Manager that makes managing your own little database quite a bit easier than typing sql commands on a command line:
https://addons.mozilla.org/en-US/firefox/addon/5817

Good thing then that you don't need Flash to use and view videos on YouTube: Fast Video Downloader and, my favorite, youtube-dl.

Please try this and file a bug report:

1. Enable session saver (Options/Main/Startup: "When firefox starts": "show my windows and tabs from last time")

2a. Enable "clear private data on exit" (Options/Privacy/Private Data: Enable checkbox "Always clear private data when I close firefox")

2b. Click the "Settings" button and make sure "browsing history" is selected.

Now open a few tabs to different pages, then exit and restart firefox. What happens? All of your tabs from the last session are gone.

Expected behavior: history of past sites should be cleared, but the CURRENT sites that are open should not be.

Actual behavior: All history is cleared, as well as the tabs that were saved in the session.

Rationale: If the user doesn't want to have tabs re-opened when they start the browser, they can disable session saver.

This is a bug but because of incorrect logical thinking, it has been marked "wontfix". You can see the bug here:
https://bugzilla.mozilla.org/show_bug.cgi?id=398817

This is a privacy bug because it removes the ability of people to clear their history while still retaining sessions, and therefor people will disable clearing of history altogether.

I get all the benefits of no flash, but can still watch youtube and all the rest if I change my mind with no hassle.

No, a change has been made since beta5 that the EULA has to be accepted by the user. Guess what? I just removed firefox, including my profile, and decided to get rid of thunderbird and seamonkey as well before they make the same change. I don't agree to their EULA, and I didn't need to agree to it to use their software in the past. Now they changed that. Now I don't use their software anymore.

Mozilla is making some interesting static analysis plugins for GCC. It looks like something that could be easy to utilized by open source projects.
See Dehydra static analysis tool

Hi, I see you feel strongly about this. But I'm not sure whether you're aware of running 32-bit browser plugins in 64-bit browsers via nspluginwrapper, and contributing to the Tamarin Project to move the just-in-time compilation and garbage collection to a 64-bit memory space. http://gwenole.beauchesne.info/projects/nspluginwrapper/ http://blogs.adobe.com/penguin.swf/2006/10/whats_so_difficult_64bit_editi.html http://www.mozilla.org/projects/tamarin/ You can get what you want now, and contribute to getting what you want in the future. Useful...? jd/adobe

Ah, quit yer trollin. AdBlock Plus is listed as compatible with Firefox 3. Download Firefox 3 RC 1 and AdBlock Plus already.

I've used Linky in the past to list urls. It doesn't work on the RC1 yet, however.
https://addons.mozilla.org/en-US/firefox/addon/425

And if you're having problems narrowing down a search in google, you could try just using the search on the Firefox extensions website. You're more likely to get what you want there.

The bug was only filed today:
https://bugzilla.mozilla.org/show_bug.cgi?id=434180 (and it seems by a /.er)

It's not one I've encountered since I don't routinely open lots of tabs in one go. If no one files a bug, it won't get fixed! And until now no one had. now it's on bugzilla, hopefully it'll be fixed in time for the next release.

I had the same halting problem on my ubuntu box, but it went away on it's own after a couple of days. It seems it was the anti-phishing database update causing the problem. https://bugzilla.mozilla.org/show_bug.cgi?id=430530

If like me you prefer typing urls and find the Awesomebar intrusive, this is how to make it so you don't feel the urge to rant like the AC above.

1) Download Oldbar from Mozilla.org https://addons.mozilla.org/en-US/firefox/addon/6227. This makes it look like the FF2 addressbar.

Then, open about:config and:
2) Edit this key browser.urlbar.maxRichResults and set the value to 5 or 6.

3) Most importantly create this key: browser.urlbar.matchOnlyTyped type Boolean Value: true

The Awesomebar will now behave almost like the FF2 addressbar.

A bit early? It was originally promised in late April!

And some may just not work correctly: https://bugzilla.mozilla.org/show_bug.cgi?id=425586

Never mind, I filed it for you:
https://bugzilla.mozilla.org/show_bug.cgi?id=434180

Here, I filed it:
https://bugzilla.mozilla.org/show_bug.cgi?id=434180

Normally when I get spam I just delete it, by using trashmail and being somewhat safe about my browsing habits I've found that I only get one or two per week. However recently I've been getting spam through SMS on my phone and that's what I find really infuriating. Granted it is technically just another email, but the fact that I'm paying for this service is what really grinds my gears.

A bug similar (if not identical) to the complaint here, was filed back in May of 2000: Bug 40848 (thread) - each docshell should run on its own thread (one thread per frame).

I'm sure they'd appreciate it, though, if no-one spammed this bug. It's closed for valid (or at least not-invalid) technical/philosophical reasons- threads are evil (you can find links supporting that assertion from the bug's comments). You can also follow it to its successor meta-bug: Bug 384323 - UI responsiveness - core/platform - meta bug and its quasi-sister: Bug 91351 - UI/App responsiveness issues.

A bug similar (if not identical) to the complaint here, was filed back in May of 2000: Bug 40848 (thread) - each docshell should run on its own thread (one thread per frame).

I'm sure they'd appreciate it, though, if no-one spammed this bug. It's closed for valid (or at least not-invalid) technical/philosophical reasons- threads are evil (you can find links supporting that assertion from the bug's comments). You can also follow it to its successor meta-bug: Bug 384323 - UI responsiveness - core/platform - meta bug and its quasi-sister: Bug 91351 - UI/App responsiveness issues.

A bug similar (if not identical) to the complaint here, was filed back in May of 2000: Bug 40848 (thread) - each docshell should run on its own thread (one thread per frame).

I'm sure they'd appreciate it, though, if no-one spammed this bug. It's closed for valid (or at least not-invalid) technical/philosophical reasons- threads are evil (you can find links supporting that assertion from the bug's comments). You can also follow it to its successor meta-bug: Bug 384323 - UI responsiveness - core/platform - meta bug and its quasi-sister: Bug 91351 - UI/App responsiveness issues.

It does work with FF 3 RC1. Granted to get the latest version to work you have to go about it a round-about way.

I have my add-ons compatibility check disabled in FF via the config (though I believe this would work fine even with that enabled).

To get the newest version, you have to go directly to https://addons.mozilla.org/en-US/firefox/downloads/file/15109/firebug-1.05-fx+fl.xpi via a link and save target as like this

The .xpi is just a zip file, so open the zip and find the install.rdf file. In there there's a section like this:

[-- Firebug --]
        [em:targetApplication]
            [Description]
                [em:id]{ec8030f7-c20a-464f-9b0e-13a3a9e97384}[/em:id]
                [em:minVersion]1.5[/em:minVersion]
                [em:maxVersion]2.0.0.*[/em:maxVersion]
            [/Description]
        [/em:targetApplication]

Change the [em:maxVersion]2.0.0.*[/em:maxVersion] line from 2.0.0.* to 3.0.0.*

This will make FF think it's a valid add-on (If you don't do this and just have the compat check disabled the add-on or something knows it's not compat and won't run).

Beyond that, it's currently telling me there's 12 Errors with the comments/replying setup lol

I'm surprised at the number of people with stability problems. I tried 3.0a1 and I had instant crashes in AJAX web apps, so I decided to wait until b1 which turned out to be a good decision, because it was much more stable. Each beta has been increasingly better. I still get a couple crashes here and there but I am betting it's due to Flash or an add-on I'm using.

On Linux I use Swiftfox, which is a recompiled Firefox optimized for individual processors so it can be even a little faster than Firefox 3. Only problem is they occasionally push out a nightly build over their update package source thingy (I tend to prefer the public beta releases) but nothing that has been unstable yet.

If you're having stability problems, you really have no right to complain until you at least TRY to fix it since Firefox gives you the tools to do so. To use another car analogy, it's like complaining your car doesn't slow down fast enough so you need a different one but you haven't even tried using the brakes yet. Well not exactly but I needed to use a car analogy. Anyways here's some things you should try:

1. Try running Firefox in safe-mode. If the problem goes away it's very likely a bad extension.
2. Try making a new, temporary profile. If the problem goes away it might be easy to fix by migrating individual files over and skipping the one that causes the problem. Also this helps to clear out old FF2 files you don't need anymore (especially if you can figure out what the files are, not hard to do since they're mostly well named).
3. If the problem occurs on pages which utilize a specific plugin try disabling the plugin... about:plugins can help you locate the dll to temporarily move it somewhere else to disable it (Firefox won't let you follow about: links so copy/paste the url). If it's a plugin you can't live without try seeing if there's updates for it.
4. Google Gears instantly crashes FF3 if sites try to use it (in b5 at least). Disable it until it gets an update.
5. Silverlight doesn't support FF3 yet and just refuses to run at all. MS is supposedly working on it.
6. Some people have reported weird slow-loading problems. I had that problem as well and traced it to the Firebug extension, or perhaps the Firecookie one... the problem is sporadic so it's difficult. However a Firebug update recently seemed to fix it. You can try disabling it if you have problems.

If you still have problems it's likely a problem with Firefox, in which case I suppose you could complain, but it would be more productive to file a bug report to increase the chances of it being fixed. To quote GLaDOS, "Thank you for helping us help you help us all."

Btw anybody on ubuntu 7.10 needs to install ca-certificates, for automated bug reporting to work #407748
sudo apt-get install ca-certificates

That should fix, "there was a problem sending your bug report".

Oldbar

I personally don't see why people don't like the new awesomebar. Selection rows are taller but unless you run on a 800x600 monitor I really don't see how it's a problem. With the bigger rows that can show more info in there, including page title, url, bookmarked status, favicon, and your tags. The oldbar can't show your tags or whether you bookmarked it, and it has less room for the rest.

Hmm, on the page you linked I read:

* Mozilla Firefox (nightly builds from 2007-11-29 to 2007-12-17)

Eventually it's better to look here: https://addons.mozilla.org/en-US/firefox/addon/6227

MOZILLA FIREFOX END-USER SOFTWARE LICENSE AGREEMENT

Version 3.0, May 2008

A source code version of certain Firefox Browser functionality that you may use, modify and distribute is available to you free-of-charge from www.mozilla.org under the Mozilla Public License and other open source software licenses.

The accompanying executable code version of Mozilla Firefox and related documentation (the "Product") is made available to you under the terms of this Mozilla Firefox End-User Software License Agreement (the "Agreement"). By clicking the "Accept" button, or by installing or using the Mozilla Firefox Browser, you are consenting to be bound by the Agreement. If you do not agree to the terms and conditions of this Agreement, do not click the "Accept" button, and do not install or use any part of the Mozilla Firefox Browser.

During the Mozilla Firefox installation process, and at later times, you may be given the option of installing additional components from third-party software providers. The installation and use of those third-party components may be governed by additional license agreements.

1. LICENSE GRANT. The Mozilla Corporation grants you a non-exclusive license to use the executable code version of the Product. This Agreement will also govern any software upgrades provided by Mozilla that replace and/or supplement the original Product, unless such upgrades are accompanied by a separate license, in which case the terms of that license will govern.

2. TERMINATION. If you breach this Agreement your right to use the Product will terminate immediately and without notice, but all provisions of this Agreement except the License Grant (Paragraph 1) will survive termination and continue in effect. Upon termination, you must destroy all copies of the Product.

3. PROPRIETARY RIGHTS. Portions of the Product are available in source code form under the terms of the Mozilla Public License and other open source licenses (collectively, "Open Source Licenses") at http://www.mozilla.org/MPL. Nothing in this Agreement will be construed to limit any rights granted under the Open Source Licenses. Subject to the foregoing, Mozilla, for itself and on behalf of its licensors, hereby reserves all intellectual property rights in the Product, except for the rights expressly granted in this Agreement. You may not remove or alter any trademark, logo, copyright or other proprietary notice in or on the Product. This license does not grant you any right to use the trademarks, service marks or logos of Mozilla or its licensors.

4. PRIVACY POLICY. You agree to the Mozilla Firefox Privacy Policy, made available online at http://www.mozilla.com/legal/privacy/, as that policy may be changed from time to time. When Mozilla changes the policy in a material way a notice will be posted on the website at www.mozilla.com and when any change is made in the privacy policy, the updated policy will be posted at the above link. It is your responsibility to ensure that you understand the terms of the privacy policy, so you should periodically check the current version of the policy for changes.

5. WEBSITE INFORMATION SERVICES. Mozilla and its contributors, licensors and partners work to provide the most accurate and up-to-date phishing and malware information. However, they cannot guarantee that this information is comprehensive and error-free: some risky sites may not be identified, and some safe sites may be identified in error.

6. DISCLAIMER OF WARRANTY. The product is provided "as is" with all faults. To the extent permitted by law, Mozilla and Mozillaâ(TM)s distributors, and licensors hereby disclaim all warranties, whether express or implied, including without limitation warranties that the product is free o

Spam is of course a complex matter but anyone who wishes to avoid myspace can always install the Firefox extension amionmyspace
https://addons.mozilla.org/en-US/firefox/addon/6067

Sadly not yet updated for the latest version of Firefox, but always amusing when you think you clicked on something important that turned out to be an Ivy-Leaguer's spring break pictures of a really stooopid drunken party.

What? No? Happens to me all the time...

You can also eliminate loads of timewasting (ie not on slashdot) and delete your existing web2 social network accounts. In the reason field select "other" and enter "I am leaving the Internet forever". Curiously this will result in lots of real phone calls and messages from the friends you never knew you had, telling you that your Bebo (fill in social website name) account is not working.

Try the MediaPlayerConnectivity Firefox addon.

Mozilla stopped supporting Firefox 1.5 in May 2007- 7 months after 2.0 was released. I'd imagine support for the 2.0 branch may be a bit longer than that but it certainly wouldn't be more than a year. FF3 may not be supported in 3 years but by the time it isn't getting security updates from Mozilla Hardy Heron will be close to EOL anyway.

They should find an ISP that supports v.92 and made sure they're running a good ad filter (and probably something like Flashblock). Dial-up is survivable if you can kill the rich media ads.

Some ISPs also offer a "web accelerator" service that'll repack images and compress HTML for you.

The VM does, however, make most JavaScript implementations look slow -- emphasis on "most".

Which is why the Tamarin project exists.

I mentioned this above, but I'll reiterate it here. In that benchmark, LOWER IS BETTER. The brand-new Flash 9 VM engine did excellent (as I expected it would), but the Flash 7 and 8 engines were generally creamed by the Javascript engines. Which I don't think is what you're trying to prove at all.

The secret to the performance of Flash 9 is this little beauty: http://www.mozilla.org/projects/tamarin/

A fully modern, high-performance, Just In Time compiler that gives the JVM a run for its money. It's an amazing piece of Javascript technology that Adobe has donated to the Mozilla project for inclusion in the next major revision of FireFox. Wonderful, wonderful engine that absolutely no one is using yet.

See, if you compiled to Flash 7 or 8, you're still triggering the Flash 8 engine. The Flash 9 engine is a complete rewrite that only works with Flash 9 content. So the next chapter of performance wars has yet to be written.

Q.E.D.

The language pack was not infected with the trojan itself. It only contained some HTML code displaying ads in the help files. These were inserted BY the trojan, on the language pack contributor's infected computer, but the language pack itself only contained the ad-displaying code.

"the author's local network was infected with the virus, so it modified html files. The main virus is a Win32 program. The infected code just display annoying banner but it can't propagate." -- https://bugzilla.mozilla.org/show_bug.cgi?id=432406#c10

I'm replying to this thread to put this information at the top of the discussion because the article summary makes it sound like the language pack actually infected people's systems with the trojan.

Even if the extension updates were signed by Mozilla (and starting with Firefox 3.0 extensions not hosted at https://addons.mozilla.org/ will need to be signed), it wouldn't make a difference unless the extension's source code was actually checked.

It is extremely trivial to create an extension that, in addition to doing what it says it does, also steals bank account info or something similar. It's also relatively easy to spot extensions that do so by doing a code check, but I doubt every extension is code checked. Also someone could theoretically make their code so hard to read that something like this could slip through even if reviewed.

Every extension submitted to Mozilla has to be approved before it will show up on Mozilla's add on site, but the approval process appears to be simply to install the extension and see if it installs correctly and doesn't break Firefox. From my experience they don't even test the extension since I've accidentally submitted updates that were completely broken, yet they were accepted.

Maybe new addon authors are scrutinized more, but I haven't seen much oversight personally. If any extension reviewer wants to set me straight I'd love to hear what's actually done.

Mozilla has an actual 16 person quality control team, probably as many as a comparable proprietary product.

The trojan itself uses a Windows-specific exploit, so Linux users will be safe.

Interestingly, Google has founded an open-source security group to coordinate responses to threats like this.

What the fuck are you talking about?

Depends. I can start keeping count if you want, but anywhere from 800-5000 backscatters would not surprise me in any given week. That, plus 1200-7000 spam messages a week.

I now have four filter mechanisms at work:
1) All my contacts get a unique email address. Something along the lines of your-name@my-server.com
2) Spamassasin on the server.
3) Thunderbird's standard junk mail filter on the client.
4) Whitelist addresses of known contacts to my "whitelist" folder.

I see maybe 10-20 spam messages a day in my inbox, and the only time I get spam in my whitelist box is when a contact of mine is irresponsible with my address. I then change the address, scold the contact, and give him a new address until next time. I could not do this without the terrific Virtual Identities Thunderbird extension, which remembers which addresses I use to email each contact:
https://addons.mozilla.org/en-US/thunderbird/addon/594

The Inbox gets about 10-20 spams a day, the Tbird junk mail gets around 200 I think, and about once a week or three I grep the spamassasin folder on the server for anything interesting.

Spam costs me money, bandwidth, and time away from my studies, work, and family. Spam is the modern Chinese water tourture: one drop does nothing, but drop after drop my life is being eroded. Not just online life, mind you, but real life as the internet is no less important to everyday life than the telephone is today.
http://what-is-what.com/what_is/spam.html

The year is something like 10 years PAST the time you should be running with JavaScript off.

You are correct here. You should have turned off javascript 10 years ago and left it that way. Welcome to the new world, one full of interesting and dangerous things like XSS exploits.

Seriously though. It's ok to use javascript for functionality that can't be provided without it. When you use javascript to implement a shopping cart, and then BREAK THE ENTIRE SITE for people who are just browsing and don't want to run the shopping cart script right now, that's just stupid.

BTW Refresh Blocker will make the site usable again.

• Wikipedia article
• 06 ALA article

• Screen size problems - Flash content is generally designed for desktop resolutions. This can be overcome with an iPhone(ish) interface
• CPU Speed problems - Flash can be a hog
• CPU architecture not supported by Adobe - only x86 and PPC are supported

> Local variables are local to the whole function

That's being fixed. See http://developer.mozilla.org/en/docs/New_in_JavaScript_1.7#Block_scope_with_let for some documentation. With any luck, ECMA will standardize this as part of EcmaScript 4.

IronPython targets the Common Language Infrastructure (e.g. Mono and .NET), not the JVM. Also, nowadays much of PyPy is written in C, so it's not going to run on IronPython (or any other Python implementation).

Anybody seriously wanting to run Python in web browsers should look to IronMonkey.

http://www.mozilla.org/rhino/

I have done my own testing on usability while making a Firefox extension and Thunderbird extension for importing photos to F-Spot ( https://addons.mozilla.org/en-US/firefox/addon/7091 ). The first thing I realized is that sometimes as a designer, you start to get tunnel vision. If you have to add a dialog to explain a button, that might be a sign that the button should not be there period, should be moved, or changed into some other kind of element. The other thing I learned is my mother gets pissed off because "I keep changing things".;-)