See below, which strange things can happen when you won’t end your line with a semicolon.
Javascript errors because of the order of javascript functions mixed with jQuery plugins…
http://jsfiddle.net/bpsuW/11/

foo is a simple javascript function.
Baz is a simple self running jQuery plugin. (because of the parentheses surrounding it).

foo = function(){
alert("function 1");
}

(function(){
$.fn.Baz = function(opt){
alert("function 2");
}
})(jQuery)


See below the script, without strange javascript errors.
http://jsfiddle.net/bpsuW/10/

The answer is really logical.
Because there is no semicolon, the jQuery plugin (Baz) will directly execute, because of the parentheses.
Like it’s a parameter of the javascript function you wrote before. (foo), and then throws errors.
So:

foo(Baz)

When you mix your jQuery plugins with native javascript classes and functions in different orders; these kind of errors can happen.
This scenario above shows you why you should always end your statements with a semicolon.

Create the startup files and folders via:
https://addons.mozilla.org/en-US/developers/tools/builder/9b0cddaa3fc073e50a0e7e284ef64438

Prefill all the fields, and build the zip file.
Unpack this zip file, and open:
/chrome/content/overlay.js

You can edit this file.
In chrome/skin/ are the files for editing the styles and logo.

After changing the files. Zip it in and rename the zip file to the xpi extension.
Drag the xpi file in your FF browser.. And your own plugin is installed.

More info:
https://addons.mozilla.org/en-US/developers/docs/getting-started
https://developer.mozilla.org/en/Code_snippets/Tabbed_browser
https://developer.mozilla.org/en/XUL/tabbrowser#m-loadURI

It’s really easy to create your own Chrome Extension.
This simple extension just opens your personal website in a new tab.

1. Create a folder
2. Create the following files:
* manifest.json
* background.html
* icon.png
3. Edit the manifest file:

{
  "name": "My website",
  "version": "1.0",
  "description": "Just browse to my website...",
  "background_page": "background.html",
  "browser_action": {
    "default_icon": "icon.png",
    "default_title": "My website"
  },
  "permissions": ["tabs"]
}

4. Now edit the background.html file:

< html>
< head>
	< script>
	chrome.browserAction.onClicked.addListener(function(tab) {
		var createData = {
			url: "http://www.ladysign-apps.com"
		}
		//you can also specify a callback after page load...
		chrome.tabs.create(createData);
                //or to load a new window:
		//chrome.windows.create(createData);
	});
< /script>
< /head>
< body>
< /body>
< /html>

From the background.html you can include any other file you want to include in this package.

5. Now open Chrome.
6. Open de extension tab: (Chrome Dev icon) > Extra / Tools > Extensions
7. Click the load button, and point to your folder, to test extension.
You will see the extension is added next to your addressbar.

Works?
8. Now pack it: – Press the pack button; and point to your folder again.
Chrome will now create a plugin of it; with an *.crx in the filename.
It will also create *.pem key file, so it identifies your plugin for further updates…

Today I found out a very strange thing… My jQuery Mobile website doesn’t work on iPhone Safari in 3G mode. In WIFI mode my page is fully loaded, and jQuery Mobile works fine.
I enabled debug messages on my iPhone. And then I found out that jquery.min.js gives me parse errors.

Parse errors jQuery.min.js
From jQuery 1.5 and higher.. You’ll receive parse errors in jQuery and therefore also jQuery Mobile can not be loaded. – And probably also not the other scripts that use jQuery.

javascript parse error line 3.
Can't find variable jQuery.

The problem seems to be with the mobile carrier’s transparent proxy. In this case T-Mobile / O2.
I tethered my phone so that I could browse on 3G and the file downloaded is completely different from that downloaded through my wired connection. Also, the downloaded files MD5 sums didn’t match!

Check this:
3G:

H TTP/1.1 200 OK
C ontent-Encoding: gzip
S erver: Apache/2.2.9 (Unix) PHP/5.2.6
E tag: "360ce-164ce-4a4b742e336c0"
A ccept-Ranges: bytes
C ontent-Type: application/javascript
A ge: 1317
D ate: Thu, 16 Jun 2011 14:56:25 GMT
L ast-Modified: Thu, 02 Jun 2011 09:28:35 GMT
E xpires: Fri, 17 Jun 2011 14:56:25 GMT
T ransfer-Encoding: chunked

Wired:

H TTP/1.1 200 OK
D ate: Thu, 16 Jun 2011 15:29:06 GMT
S erver: Apache/2.2.9 (Unix) PHP/5.2.6
L ast-Modified: Thu, 02 Jun 2011 09:28:35 GMT
E tag: "360ce-164ce-4a4b742e336c0"
A ccept-Ranges: bytes
C ontent-Length: 91342
K eep-Alive: timeout=5, max=100
C onnection: Keep-Alive
C ontent-Type: application/javascript

How to solve?
Don’t serve your jQuery file yourself but use a CDN like google:
http://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js

This did the trick!

I noticed this bug: my Google Visualization Charts were not working in FF3.6
Strange enough it did work in all of the other browsers I tested (Chrome, FF4, IE7, IE8); deeping this problem down, I found out that Google Visualization Charts do work in FF3.6, but not when loaded from Typo3 CMS.
Then I noticed that this bitch made the bug:

– Typo3 is setting a base path. The reason why Google Visualization API is buggy, is because they use relative paths.

Here’s the fix for Mootools:

      google.setOnLoadCallback(drawChart);

		/**
		 * Google Visualization API crashes because of base href tag in TYPO3
		 * Quickfix
		 */
		function fixGoogleCharts(){
			var arrIframe = $(document.body).getElements('iframe[id*=Drawing_Frame_]');
		    arrIframe.each(function(el){
				var content = $(el).contentWindow.document.body;
				var arrG = ($(content).getElementsByTagName('g'));

				for(var i = 0; i<arrG.length; i++){
					if(arrG[i].getAttribute('clip-path')) {
						arrG[i].setAttribute('clip-path', 'url(' + document.location + arrG[i].getAttribute('clip-path').substring(4))
					}
				}

		    });
		}