For surface streets, how about telling me the name of the street before the turn? At least in the San Francisco area, it's difficult to see the names of streets until you're so close that it's too late to make a turn legally.
For a web site to install software, you have to have that option checked and have the site whitelisted and click the "Install" button in a security dialog when the site tries to install software. The option's name is scarier than what the option actually does.
This exploit has two parts: an XSS hole and a hole that lets xpi-installation-whitelisted sites execute arbitrary code. Your workaround only fixes the second part and leaves you open to an XSS hole, which is sufficient for stealing your saved passwords, cookies, secret pages on your intranet, etc. The real workaround is to disable JavaScript.
If you don't like live preferences, there's a hidden pref you can toggle to turn them off. I like live preferences, so I turned them on (I'm using Windows).
David Baron, a Mozilla Foundation employee and one of the strongest Gecko hackers, has been spending a lot of his time fixing memory leaks in Gecko and Firefox.
* Keyword stuffing may put this page a little higher in search results, but the kind of people who would search for "traffic estimator" are unlikely to click on an obviously keyword-stuffed search result.
* This undermines Google's reputation as having unbiased search results.
Slashdot Mirror
I belive the magical tool you are looking for is called the LART.
Query by Humming at CS.NYU works for me some of the time.
For surface streets, how about telling me the name of the street before the turn? At least in the San Francisco area, it's difficult to see the names of streets until you're so close that it's too late to make a turn legally.
Yes.
I'm pretty sure there are no Whats on my network.
or does "proactive anti-virus" sound like an oxymoron?
Can you give me more information about these security holes in Windows Explorer?
Online price customization has more in common with grocery coupons than with grocery loyalty cards.
Extension writers don't have to parse history.dat. They can access History using RDF (example 1, example 2).
How'd I Get Here
1.0.4 was a minor update. 1.1 will not be.
E4X is a standard published by the same group that publishes the ECMAscript standard. I don't think the array extras are described by any standard.
This entry in Asa Dotzler's blog contains links for downloading this release candidate of Deer Park Alpha 1.1.
The article has links to New Web Developer Features and New Extension Developer Features. There's also a page listing New Browser Features and an unofficial page listing Notable bug fixes.
This isn't a case of 'embrace and extend'... Any web developer using these for public apps is clearly a butt-head.
Couldn't you have used the same argument to defend IE's extensions to DOM?
Verisign, truste, paretologic, and maybe more (the page isn't clear).
Greasemonkey user scripts also have access to magical functions, but they're not the same ones Opera user scripts have access to.
For a web site to install software, you have to have that option checked and have the site whitelisted and click the "Install" button in a security dialog when the site tries to install software. The option's name is scarier than what the option actually does.
This exploit has two parts: an XSS hole and a hole that lets xpi-installation-whitelisted sites execute arbitrary code. Your workaround only fixes the second part and leaves you open to an XSS hole, which is sufficient for stealing your saved passwords, cookies, secret pages on your intranet, etc. The real workaround is to disable JavaScript.
If you don't like live preferences, there's a hidden pref you can toggle to turn them off. I like live preferences, so I turned them on (I'm using Windows).
David Baron, a Mozilla Foundation employee and one of the strongest Gecko hackers, has been spending a lot of his time fixing memory leaks in Gecko and Firefox.
And don't get sued, because your settlement will fund their lawsuits too.
Google occasionally makes search results go through a redirect, so it has statistics about which results users clicked on for maybe 1% of searches.
/* Get the OVERFLOW attribute. (Fuck yuo, W3C. Fuck you.) */
/* Words cannot express how much HPUX SUCKS!
** This whole hacky pile of poop was done by Michael Toy.
I got a check from AdSense and I haven't made $100 the whole time I've been using it.
* Keyword stuffing may put this page a little higher in search results, but the kind of people who would search for "traffic estimator" are unlikely to click on an obviously keyword-stuffed search result.
* This undermines Google's reputation as having unbiased search results.