Slashdot Mirror

How about Mozilla firefox (or any of it's extensions).

Sadly, when Javascript gets mentioned most people think of browser scripting. That's like thinking of MFC every time C++ gets mentioned... :(

What sorts of shells interpret JS? I know of Mozilla's js shell, and they also have a xpcshell (which adds XPCOM things to make it fully Mozilla-y). Sadly js shell has no built-in file access (it's a compile-time option you have to jump through hoops to enable, and buggy), and xpcshell has lots of XPCOM baggage.

Are there any others using different engines? Anything from Adobe (ActionScript) maybe?

I don't get what all this hype about the Acid2 test is about - its not even a standards test! By their own admission it's a "means of exposing the ability of user agents to handle invalid CSS properly" (source).

I'd rather browser makers worked on fixing bugs (may take a while to load) and more rich features.

Some do. Mozilla, for one. I imagine there are others out there too.

In Firefox, you can do it one better with an addon.

I recommend Permit Cookies.

I can't wait for the Mozilla devs to clean up their cookie code so that blocking cookies is as easy and configurable as blocking images.

I can't wait for the Mozilla devs to clean up their cookie code so that blocking cookies is as easy and configurable as blocking images.

At the risk of wandering off topic (eh, too late I guess), the Tab Mix Plus extension (and probably at least a couple other extensions) has a "Single Window Mode" option, where anything that would otherwise open in a new window opens in a new tab instead.

It is a known problem. Office apps export bad html (go figure). Bug listed here: https://bugzilla.mozilla.org/show_bug.cgi?id=10213 1

"Net Usage Item"
https://addons.mozilla.org/firefox/225/

"Usage Counter"
https://addons.mozilla.org/firefox/3482/

Not exactly what you're looking for, but maybe a start?

"Net Usage Item"
https://addons.mozilla.org/firefox/225/

"Usage Counter"
https://addons.mozilla.org/firefox/3482/

Not exactly what you're looking for, but maybe a start?

At the risk of asking a dumb question, how do you specify a user agent? Is there an easy way of doing this?

There is a bug about this but it was closed as WONTFIX. :(
https://bugzilla.mozilla.org/show_bug.cgi?id=34725 9

If a lot of people vote and leave comments perhaps someone will reopen it.

By all means keep using the extension (which probably does the same thing). If enough people install the extension maybe it'll be a "vote" for getting this changed back in FF3. Slim hope, but at least it's something.

Oh, and leave feedback at http://hendrix.mozilla.org/ about this and other complaints

Funny, the actual website for the alpha pointed me here: http://releases.mozilla.org/pub/mozilla.org/firefo x/releases/granparadiso/alpha1/

Note that it's not the same as the latest trunk build. The name aside, it's dated December 7, not December 13.

Funny, the actual website for the alpha pointed me here: http://releases.mozilla.org/pub/mozilla.org/firefo x/releases/granparadiso/alpha1/

Note that it's not the same as the latest trunk build. The name aside, it's dated December 7, not December 13.

From what I have read, No.

Basically, they are dropping support for anything prior to Win2k. They have no developers who either have the knowledge to work on pre-Win2k OS's or the ones they have are overburdened with other responsibilities.

They need someone who knows how to code for pre-Win2k machines.

Here is the link to a discussion on MSFN forums. The poster ivanbuto started this thread to attempt to find someone who could look into extending support.
http://www.msfn.org/board/lofiversion/index.php/t7 2957.html

And here is the Bugzilla discussion in which he started asking questions about this.
https://bugzilla.mozilla.org/show_bug.cgi?id=33027 6

That Bugzilla discussion gives pointers on what one can do to get Pre-Win2k support implemented. You just have to weed those out. It also lists a dev who is willing to review a patch that would give Pre-Win2k support.

Perform a google search for the terms "firefox", "memory leak", and "about:config".

The "leak" isn't a bug, it's a feature--really. Pages in history are cached to allow faster display times, and when you have multiple tabs open, this creates a huge drain. Try setting the value to -1, as this disables the feature completely.

And for developers, there's a leak detector extension. Search addons.mozilla.org for it.

See http://www.mozilla.org/projects/svg/status.html From what I can see, pattern, and foreignObject support have been added since Gecko 1.8.1.

Recent nightly builds for Mac OS X feel much snappier than Firefox 2.0. One of the obvious culprits is that Cocoa widgets are now used on Mac OS X builds. I don't know if there are other changes affecting the performance on Mac OS X, but the difference is fairly dramatic.

I love Firefox on Windows, but I have stuck with Safari on the Mac because Firefox has always felt porky and slow compared to Safari on the same hardware. The newer builds of Firefox 3 for the Mac are much better: windows, tabs, menus and other user interface elements have a nice immediate feel to them. And the page rendering is more performant than Safari on certain Web 2.0 type sites like digg and Slashdot's new discussion system. It's buggy alpha code, but early indications seem to be good for a nice improvement on the Mac when Firefox 3 comes out.

"Firefox 3.0 Alpha has been available since August 31, 2006. I love posting every Firefox update as much as the other guy, but get on the ball or don't bother."

Sorry, you are mistaken. Gran Paradiso Alpha 1 aka Firefox 3 Alpha 1 was released on December 8th.

Trunk/Nightly builds have long had the "alpha1" mark as a sign that they will lead to "alpha1" in the future.

To get the builds that have the reflow branch landed (hence passing Acid2 (although the nose is 1px off)) you need to use the nightlies which are named Minefield.

Take note of the codename for it before trying it, though recently it has been quite stable.

To get the builds that have the reflow branch landed (hence passing Acid2 (although the nose is 1px off)) you need to use the nightlies which are named Minefield.

Take note of the codename for it before trying it, though recently it has been quite stable.

But will it pass Acid 2?

Ahem...Download link for Alpha1 - http://ftp.mozilla.org/pub/mozilla.org/firefox/nig htly/latest-trunk/.
See, it's latest-trunk.

Use the Video Downloader firefox plugin: https://addons.mozilla.org/firefox/2390/

Then use VLC http://www.videolan.org/vlc/ to play the resulting file.

Firefox: http://getfirefox.com/
Adblock: https://addons.mozilla.org/firefox/10/
NoScript: https://addons.mozilla.org/firefox/722/

Firefox: http://getfirefox.com/
Adblock: https://addons.mozilla.org/firefox/10/
NoScript: https://addons.mozilla.org/firefox/722/

NoScript "This whitelist based preemptive blocking approach prevents exploitation of security vulnerabilities (known and even unknown!) with no loss of functionality... Experts do agree: Firefox is really safer with NoScript ;-)"

Or use NoScript, which also blocks the flash if you set it in the options.

• Minimo (MPL)
• Links (GPL)
• Lynx

Check out the Firefox extension Shazou, it gives you the location of any server in a google maps window. This particular server is in Rome.

As pointed out, the Times site isn't fooled, but there are a good many out there that are fooled. Sometimes if you ever do a Google search, one of the results will contain a keyword or two. However, when you click on the link, you'll find yourself redirected to a subscription page. Useragent spoofing can frequently show you the same page that Google indexed.

If you're a FF user, grab the Useragent Switcher extension and add in a UA of "Mozilla/5.0 (compatible; googlebot/2.1; +http://www.google.com/bot.html)". You'll then be two clicks away from seeing what was previously registration-only.

Hey, any code base that includes a "libpr0n" module can't be all bad.

>First, for passwords, you only need to remember *1* and have the following javascript (which runs client side) from this most excellent site:
GenPass.

Quite a few options for this functionality. Last time I reviewed them, my favorite was pwdhash.

The Firefox codebase is indeed a mess. Don't take my word for it, view it yourself: http://lxr.mozilla.org/seamonkey/source/.

Part of the problem is the severe over-architecturing. This over-architecturing has added much unnecessary complexity to the overall design of Gecko and Firefox. Much of it is "justified" in the name of portability. But then we find that other frameworks, including wxWidgets and GTK+, do just fine without the overly complex and confusing architecture of Gecko and Firefox.

It's just not easy for most developers to become up-to-date with the Mozilla codebase because of all this added complexity. Unless a volunteer developer has literally months to spend learning even the small portion of the code they're interested in working on, it's basically inaccessible to most programmers.

The constraints of the real-world often come into play, and we have developers modifying code they don't necessarily understand fully. And so we get the frequent crashes, glitches, memory leaks and security problems that Firefox 1.5.x and 2.x have become famous for.

It's likely that Mozilla should ideally rewrite a vast portion of their code, keeping simplicity in mind. That likely won't happen, and thus we will most assuredly still run into problems with Firefox and Gecko, problems caused directly by the overcomplication of the Mozilla architecture.

Enter XULRunner. Democracy Player uses it ... when FF and TB will is another story, I suppose. I guess since their development is ahead of XULRunner's curve (XULR is based on FF 1.5.0.4's codebase), it'll be a while.

Firefox: NoScript.
Extra protection for your Firefox: NoScript allows JavaScript, Java and other executable content only for trusted domains of your choice, e.g. your home-banking web site. This whitelist based preemptive blocking approach prevents exploitation of security vulnerabilities (known and even unknown!) with no loss of functionality... Experts do agree: Firefox is really safer with NoScript ;-)

1. Phishing attacks are becoming more common, and obviously, it is necessary for all users to be more cautious about exactly where they are entering their passwords -- this means being very alert to the contents of the URL bar (so as to not be deceived by things like "http://www.google.com.blahblah.phisher.tripod.com /google..."), and also not being misled by javascript window-within-window things that make something else look like the URL bar, etc. All this probably requires a greater level of attention than is within the capabilities of, say, old people (or even those teenagers on MySpace). So how do you make sure you don't give away your password to the wrong guys?
2. A common phishing-like attack is to somehow hack into some low-security site and get some username-password pairs, then try them at other sites. As you might guess, this trick is quite effective, because most people use the same password everywhere. Remembering hundreds of different hard-to-guess strings is somewhat hard, after all.

I'd recommend using the Stop Autoplay extension for Firefox. It works just like Flashblock, but for movies and sounds. And it blocks background sounds and music as well.

Extra protection for your Firefox: NoScript allows JavaScript, Java and other executable content only for trusted domains of your choice, e.g. your home-banking web site.
This whitelist based preemptive blocking approach prevents exploitation of security vulnerabilities (known and even unknown!) with no loss of functionality...
Experts do agree: Firefox is really safer with NoScript ;-)

Try NOSCRIPT. I cannot visit a website without it. You can choose what javascripts to allow: https://addons.mozilla.org/firefox/722/\\ Don't blame slashdot. It's all about the $$

Sorry, going to be almost entirely off-topic here because a submission on this was rejected and I think it deserves at least some exposure. If it was Outlook eating e-mails Slashdot would be having a field day, but alright.

ThunderBird v1.5.0.8 introduced an issue where malformed e-mails (namely the Referer: header value matches the Message-Id: header value) is causing the e-mails not to be displayed. They are received, they're in the mailbox file, but they're not displayed. The error is probably somewhere in the Threading code, but affects non-threaded Views all the same. Worse yet, if you compact your folders (as you are recommended to do regularly), the invisible e-mails will also actually be deleted.

This issue has been in ThunderBird since 1.5.0.8 release, obviously. It was first discovered on November 9th. A bug was logged on November 11th. It is now December 1st (here anyway), and an official fixed release is not expected until later this month.

There is no telling how many users are affected by this bug, as most users will never realize that the mail isn't arriving - and when told, the first few things they would check is spam filters, their ISP's spam filters, firewalls, junk filters, and then the MozillaZine page on disappearing e-mail (sad that there's such a page) - which makes no mention of this bug either.

I'll take an exploit any day - turn my machine into a zombie if you must - but causing me to lose mail for no good reason, knowing about it, and not officially fixing it, is inexcusable.

That said - the fix is in the 1.8 branch, in 2.0, and in the nightly builds. Thing is, only way to know about it is if you read the bug (change referrer - bugzilla.mozilla blocks slashdot referrers):
https://bugzilla.mozilla.org/show_bug.cgi?id=36040 9

Minimo is the mobile mozilla. WinCE/Mobile only. Besides that, I don't want to be the guy having the task of getting a decent Java VM running on a 486 to run Opera.

I wonder why nobody mentioned the following Firefox extension: Temporary inbox (https://addons.mozilla.org/firefox/2650/). It allows to work with disposable emails in one mouse click from the toolbar (well, maybe, two: one for email generation and one for checking).

Um, Phoenix 0.1 was around 10 MB.

ftp://ftp.mozilla.org/pub/mozilla.org/phoenix/rele ases/0.1

I've built a lot of web pages, and this has made me realize that it's incredibly quick and easy to whip up GUIs with HTML. The experience was much better than with the GUI builders I had used, and certainly beat coding GUIs by hand.

Of course, HTML is not intended as a language for describing native GUIs, so it has some limitations there. Fortunately, there is a variety of XML formats for describing real GUIs.

What makes XML so great for describing GUIs is that it's so good at describing nested objects. If you think about it, that's exactly what GUIs are: you've got your windows, with a bunch of widgets in it, one of which is a scrollable area with more widgets in it, etc. This is naturally described by an XML tree that contains all these widgets, with some attributes used for connecting them to the application; e.g. ids to allow the application to reference widgets, and embedded code to let the GUI respond to events (e.g. HTML's onclick).

Where many XML GUI languages fall short is in that they don't provide methods for building new abstractions. If you have a lot of subtrees that are all very similar (say, a frame, a title, a content window, and a hide and a show button), you'll completely have to code each of them in full. Any programming language worth its salt will provide a way to abstract over this (functions!), but I think the realization that XML GUI descriptions (and HTML documents!) are programs hasn't fully set in yet.

Next time I'm coding a GUI, I'll be generating the XML from a proper programming language. I've had good results with Lisp before...

So really, it is the firefox codebase. Seamonkey lives here:
http://lxr.mozilla.org/seamonkey/source/suite/
while firefox lives in the similar, but different:
http://lxr.mozilla.org/seamonkey/source/browser/

So really, it is the firefox codebase. Seamonkey lives here:
http://lxr.mozilla.org/seamonkey/source/suite/
while firefox lives in the similar, but different:
http://lxr.mozilla.org/seamonkey/source/browser/