Memory leaks in some situations but I can't put my finger on what is causing it.
If memory leaks bother you a lot, you might consider switching to Firefox trunk, where
* Some of the bigger memory leaks have been fixed.
* There is a tool you can use to track down (or help Firefox developers track down) what causes the remaining leaks.
Unfortunately, Firefox trunk is a bit crashy right now, at least for some users. You could follow The Burning Edge for a while and then download a trunk build once the most frequent crashes are fixed.
This wiki page also talks about some non-leak causes of high memory usage.
You have to partly disable video acceleration for some types of content to play properly in some pages.
I have neither noticed problems like this nor read bug reports like this. Can you file a bug, including information about your graphics card and driver, with at least a URL and preferably with a reduced testcase?
When the US has a "trade deficit" with Japan, Japanese companies or individuals have to be doing something with the extra money -- either investing in US companies (creating a "capital surplus") or allowing another country to import from the US (creating a "trade surpus" with a country other than Japan). The latter is sometimes called a trade triangle.
I'm not an economist either, but that's the explanation I remember from my an econ class I took a few years ago.
Phishing, fraudulent Ebay auctions and Nigerian lottery scams have nothing to do with poorly-written code. They have to do with poorly-thinking brains.
Phishing may not have anything to do with poorly-written code, but it does have a lot to do with poorly-designed protocols and user interfaces. Phishing is as successful as it is because
(1) Most email systems do not authenticate senders (even by hostname), so it's trivial to spoof email messages.
(2) Most web browsers expect users to parse URLs in their heads in order to determine what site they're on, and then parse hostnames (which happen to be written "backwards" compared to the rest of the URL) to determine whether to trust the site.
If protocols and software were better designed, phishing would only work on extremely gullible people.
Once you install Greasemonkey and my script, Firefox will automatically click the "Stop" link for you. For good measure, it also hides the slideshow-related links (slower / stop / faster), and copies copy the "previous" and "next" links to below the text so you don't have to scroll back up to click them.
No. I want to go to the next "slide" when I'm done reading the text and any associated Wikipedia articles, not when an "average reader" is done reading the text.
The bookmarks and history code is being rewritten by a team that includes Ben Goodger. They're planning to rewrite both the backend, so it uses a proper database (based on SQLite), and the user inteface, so bookmarks can become useful again. The codename for this rewrite is "Places" and it's expected to be one of the big features of Firefox 2.
A large percentage of Web users rely on history to make visited links appear differently than unvisited links. (On most sites, visited links appear purple and unvisited links appear blue, but only if you have history enabled.) A smaller percentage uses history for other purposes, such as recovering from a crash or accidentally closing a tab or window, remembering how they found a page, or determining whether their son looks at porn.
According to Mr Clarke the word, perhaps more correctly nones-event, is an event that takes place during a period of the month known as the nones by the Ancient Romans, rather like the Ides of March.
In other words, he combined two Latin-based words to solve an English version of a Greek puzzle.
Suddenly, Englishneologisms that combine Latin and Greek don't bother me at all.
From 7 things the Gmail Team is thankful for this year:
* Winning the "PC World World Class Award" for being #2 on the list of The 100 Best Products of 2005. (We don't mind being #2, especially to Firefox. Plus, it gives us more to work for.)
(The list appeared on the main page of mail.google.com on Thanksgiving 2005.)
when Slashdot said that a web browser was critical for the success of Linux on the desktop. I got involved in the Mozilla project as a result (yes, Slashdot caused something good to happen), but ironically I still don't use Linux on my desktop or laptop.
Especially since it encourages two very insecure things: a)permitting the entire hostname access b)permanently (since few users are likely to go BACK and DELETE the entry)
When a whitelisted site tries to install an extension, you basically have IE's UI (an Install/Cancel dialog). I don't see how Firefox is "encouraging insecure things" by making you whitelist a site, given that the whitelist only lets web sites pose that dialog.
(1) the server uses content-disposition: attachment. In this case, the server is arguably telling the browser "do not open this file automatically". I'm not sure why Firefox cares that the server says that, though. See bug 236541.
(2) the server uses content-type: application/octet-stream. In this case, I think it's a browser bug. I'm not sure this still happens.
What extensions are you using, if any? Sometimes leaks are due to extensions rather than Firefox itself.
Aren't your first and third points the same?
What cost isn't incorporated into the price of electricity, and why not?
Your microwave oven has a remote?
On the other hand, this might make it easier to remember to turn off your cell phone while watching a movie.
Memory leaks in some situations but I can't put my finger on what is causing it.
If memory leaks bother you a lot, you might consider switching to Firefox trunk, where
* Some of the bigger memory leaks have been fixed.
* There is a tool you can use to track down (or help Firefox developers track down) what causes the remaining leaks.
Unfortunately, Firefox trunk is a bit crashy right now, at least for some users. You could follow The Burning Edge for a while and then download a trunk build once the most frequent crashes are fixed.
This wiki page also talks about some non-leak causes of high memory usage.
You have to partly disable video acceleration for some types of content to play properly in some pages.
I have neither noticed problems like this nor read bug reports like this. Can you file a bug, including information about your graphics card and driver, with at least a URL and preferably with a reduced testcase?
When the US has a "trade deficit" with Japan, Japanese companies or individuals have to be doing something with the extra money -- either investing in US companies (creating a "capital surplus") or allowing another country to import from the US (creating a "trade surpus" with a country other than Japan). The latter is sometimes called a trade triangle.
I'm not an economist either, but that's the explanation I remember from my an econ class I took a few years ago.
Phishing, fraudulent Ebay auctions and Nigerian lottery scams have nothing to do with poorly-written code. They have to do with poorly-thinking brains.
Phishing may not have anything to do with poorly-written code, but it does have a lot to do with poorly-designed protocols and user interfaces. Phishing is as successful as it is because
(1) Most email systems do not authenticate senders (even by hostname), so it's trivial to spoof email messages.
(2) Most web browsers expect users to parse URLs in their heads in order to determine what site they're on, and then parse hostnames (which happen to be written "backwards" compared to the rest of the URL) to determine whether to trust the site.
If protocols and software were better designed, phishing would only work on extremely gullible people.
Funny that you compare it to a "trade deficit", an even more meaningless number.
They already made roofies illegal. What will I do if they make short, wide glasses illegal too?
That isn't a serious security hole (it's a permanent DoS but that's it, despite what the page claims) and it doesn't require JavaScript.
I'm not aware of any publicly known security holes in Firefox 1.5 that rely on JavaScript. Link?
When did "Web 2.0" become synonymous with "doesn't provide fallback mechanisms for when JavaScript is not available"?
It annoyed me enough that I wrote a Greasemonkey script to fix it.
Once you install Greasemonkey and my script, Firefox will automatically click the "Stop" link for you. For good measure, it also hides the slideshow-related links (slower / stop / faster), and copies copy the "previous" and "next" links to below the text so you don't have to scroll back up to click them.
No. I want to go to the next "slide" when I'm done reading the text and any associated Wikipedia articles, not when an "average reader" is done reading the text.
Why should someone have to have more than half a brain before we take their word for it that it crashes for them?
The bookmarks and history code is being rewritten by a team that includes Ben Goodger. They're planning to rewrite both the backend, so it uses a proper database (based on SQLite), and the user inteface, so bookmarks can become useful again. The codename for this rewrite is "Places" and it's expected to be one of the big features of Firefox 2.
A large percentage of Web users rely on history to make visited links appear differently than unvisited links. (On most sites, visited links appear purple and unvisited links appear blue, but only if you have history enabled.) A smaller percentage uses history for other purposes, such as recovering from a crash or accidentally closing a tab or window, remembering how they found a page, or determining whether their son looks at porn.
According to Mr Clarke the word, perhaps more correctly nones-event, is an event that takes place during a period of the month known as the nones by the Ancient Romans, rather like the Ides of March.
In other words, he combined two Latin-based words to solve an English version of a Greek puzzle.
Suddenly, English neologisms that combine Latin and Greek don't bother me at all.
Does that mean you'll be immortal until you die?
when Slashdot said that a web browser was critical for the success of Linux on the desktop. I got involved in the Mozilla project as a result (yes, Slashdot caused something good to happen), but ironically I still don't use Linux on my desktop or laptop.
Go to about:config and make browser.xul.error_pages.enabled false. (Don't be fooled by the name of the pref -- netError is mostly XHTML, not XUL.)
Especially since it encourages two very insecure things: a)permitting the entire hostname access b)permanently (since few users are likely to go BACK and DELETE the entry)
When a whitelisted site tries to install an extension, you basically have IE's UI (an Install/Cancel dialog). I don't see how Firefox is "encouraging insecure things" by making you whitelist a site, given that the whitelist only lets web sites pose that dialog.
This can happen for two reasons.
(1) the server uses content-disposition: attachment. In this case, the server is arguably telling the browser "do not open this file automatically". I'm not sure why Firefox cares that the server says that, though. See bug 236541.
(2) the server uses content-type: application/octet-stream. In this case, I think it's a browser bug. I'm not sure this still happens.
You might be able to tell which it is using web-sniffer.net or LiveHTTPHeaders.