Posts Tagged ‘firefox’

Blocking Google and Facebook Requests on other Websites

February 22, 2011

Nearly every webpage is requesting additional files from Google or Facebook servers in these days, e.g. when making use of the very much discussed Google Analytics or Facebook Like Button. Of course, there are more: Google Web Fonts, Google Charts, Google Adsense, Google Apis, Facebook Connect, Facebook Widgets, etc., etc. The list keeps growing.

Why is it bad to have third party requests in web pages?

Of course, it slows down your web experience. But what is even worse, especially when it comes to Google and Facebook: for every request to their servers a cookie (and of course, your IP) is sent along allowing them to recognize you and compile a (nearly) complete profile of your web activities. This is especially bad when you using one of their services with login, because they can attach your activity to your confirmed identity without any doubt. But be aware that they are probably tracking all of your activity even when you are logged out.

What can you do to avoid Google and Facebook violating your privacy?

Block their content. As their Third-Party-Code is embedded in nearly every website (often, you do not even see a Google or Facebook feature on the surface) you cannot simply decide not to use their features.
The Ghostery Addon for Mozilla Firefox seems to be a good way to accomplish this.

Incremental search for JavaDoc in FireFox

November 23, 2009

The following Greasemonkey userscript will add an incremental search feature to any JavaDoc displayed in the browser.

In order to use the script you’ll need the Greasemonkey addon, too:

Force page reload on back/forward button in Firefox 3.x

November 16, 2009

When using the back/forward buttons in FF3.x, pages are cached and delivered from cache very strictly. Obviously (unlike normal caching) even page headers like Pragma, Expires etc. are ignored. This special cache is often referred to as bfcache (back/forward cache).

This behavior caused exceptions in my wicket app, where ajax funtionality is used, here’s what happens:
* Load page containing panelA
* User interaction, replacing panelA with panelB using ajax
* User clicks back button
* User clicks forward button
-> initial page content (markup) is loaded from fbcache, including panelA
-> in wicket pageMap, panelA is not existent, since it has been replaced with panelB
* User interacts with an ajax element on panelA
-> exception is thrown “Component x not found on page”

Solution: add an unload handler to the page’s body tag. This causes firefox to reload the page instead of simply grabbing it from bfcache, so that server and client side state is in sync again 🙂