Firefox Quickies

First, Gypsy2012 writes with a highly critical security flaw involving both Firefox 2.0 and Internet Explorer, which could allow a malicious attacker to gain remote control of a user's system. It exploits the "firefoxurl://" URI handler. ... Next, reader dsinc sends word that the beta for Firefox 3 has slipped by 6 weeks. The new target date is September 18 at the earliest. The article wonders whether the final release will slip into 2008. ... Finally, reader jktowns points out new anti-phishing features in the latest nightly build of Firefox 3. One of them was added into the code base by the guy who developed the LocationBar² extension.

Comments

WINDOWS Firefox, how hard is that to type?

[Anonymous Coward]

Once again, another headline just calling it "Firefox" when in reality it is WINDOWS firefox that is to blame. WINDOWS, get it submitter? Grok the diff? Can't type a few extra characters?

I wish some devs would fork the linux version of FF, give it a brand new name, and then go forward and code an open source browser for an open source operating system and not be associated with that WINDOWS application or with the multi billion dollar company Microsoft that can afford to do its own coding, for the people who insist on running that operating system.

    I don't code but I would donate cash to such an effort to make a REAL open source browser for a REAL open source operating system and not stay stuck on being MS's bitch and sucking hind tit all the time.

Let's call a spade a spade, Mozilla as it is run now is a stealth arm of Microsoft corporation at this point. Their main emphasis and drive is creating MS Windows applications.

Re:Demonstration

[fatphil]

"There is no standardized way to parse command lines, and no standardized way to escape them."

If that's the case, then windows is broken beyond repair.

Firefox does not chose how to parse the command line, that happens before main() is ever called. Firefox _does_ get argc and argv. So yet again, it's not Firefox's fault. It's just doing what it's told. Whatever it is between the exec()/spawn() (lauchyadayada()) and the child's main() must have _some_ specified behaviour. If MS do not specify that bahaviour then this is even more of an OS issue than I previously thought.

Or are you saying that firefox implements its own _setargv, to get around the above issue?