Mozilla Announces Extend Firefox Contest Winners 163
Foxy Betty writes "Mozilla Corporation has announced the winners of the Extend Firefox Contest, a project initiated to encourage development of extensions for the Firefox Web browser. A panel of industry notables reviewed more than 200 extensions submitted to the contest."
improved updater (Score:2, Interesting)
A bit staid? (Score:5, Interesting)
Anyone else find it a bit anticlimactic?
Re:A bit staid? (Score:2, Interesting)
Re:Memory Leak (Score:2, Interesting)
Re:If only... (Score:3, Interesting)
Not all people are that good with HTML/Web terminology: AdBlock unfortunately use lots of it. It's okay for me. But my friend e.g. has whole bunch of extensions (a-la FlashBlock, NoScript) which in fact do what I do with AdBlock alone.
Platypus (Score:2, Interesting)
Firefox extensions I can't live without (Score:3, Interesting)
GooglePreview:
https://addons.mozilla.org/extensions/moreinfo.ph
Venkman Javascript Debugger (for 1.5):
http://getahead.ltd.uk/ajax/venkman [getahead.ltd.uk]
Live HTTP Headers:
http://livehttpheaders.mozdev.org/ [mozdev.org]
Peter
But users of other browsers can't read about them (Score:2, Interesting)
FWIW, if I use the search function (searching in extensions) from Galeon, the results returned have &application=Galeon appended to the URL, which seems to me to confirm that it is user-agent dependent.
Re:If only... (Score:3, Interesting)
I've also extended my own version of AdBlock to incorporate a new feature which I named relative-to-site blocking: you define what the "site" is with a regexp, a few special modifiers and filter non-matching content from it with a regexp. For example, the following rule:
##\dom##.*
Would block all content which is not coming from the domain currently in the status bar, so if you're surfing example.com images and javascript linked from google-analytics.com will get blocked, but if you're surfing google-analytics.com (for any reason) it allows you to watch it. Of course there is a whitelist too,
#@example2\.com##
or a regular expression like #@\tld:hu##
Then there are the two-level filters which really give the fine-tuning abilities:
###\tld:com|biz|net#####(\dom=/example/)|(\sadom)
A bit of an explanation for this one, the first regexp is a regexp deciding what kind of domains you want to match, the second regexp decides that the domain you're matching - how do you want it to be considered a site and the third part decides what kind of filtering to do with content that doesn't match your defined "site".
Currently five special "variables" exist:
\tld:top-level-domain(s)-here - Self explanatory
\dom(=/regexp/)? - Current domain you're at - like developers.slashdot.org. There is an optional regexp if you want to specify what kind of domains you want this rule to match for - useful for creating multiple-choice rules. Like the long one above.
\cdom(=/regexp/)? - Conservative domain - like slashdot.org even though you're visiting developers.slashdot.org.
\sadom(=/regexp/)? - Subdomains and domain - like
\csadom(=/regexp/)? - Conservative domain and subdomains - like *.\.slashdot.org if you're visiting developers.slashdot.org
Currently it is only used by me, I made a post about this a while back on the Adblock plus forum, but the Adblock plus devs didn't really react. I might contribute code back if there is interest though.
Re:A bit staid? (Score:3, Interesting)
Can anyone explain why a configuration daemon eats up 100M overnight? When I start it up, it only takes about 10M.
CookiePie 0.5.4 Firefox Extension (Score:2, Interesting)