• Startup pages that tell you that although your browser is up to date, your plugins are not so the next visit to youtube could send your CPU usage to 150%. They are also very vocal about specifying whose mistake it is , see the attached and here
• Safari will let the plugin malfunction but the browser will not fail – This seems the best idea but is yet to be seen at work. Although I feel Firefox 3.5 crashes more than Safari 4.
• Extensions/Add-ons that Mozilla supports seem bigger culprits as users do anything from hiding Search engine ads to full blown 3-D photo walls. Un-tested extensions are grayed out until you give explicit consent that you are ready to “experiment”

The revolution is both way and the term “Open Web” seems more realistic now as everyone starts behaving responsibly.

Update: Works in Firefox. Safari still has a 10% market share and should be supported or at least tested.

Intel, you lost my business as I got distracted writing this post rather than trying to buy a SSD from you.

When I reached the page I could not scroll using the scroll on the trackpad of my laptop, neither could I do ctrl+f an unconscious habit when I know what I am looking for.  If you watch the site carefully though it looks like a normal webpage.

Lesson learnt, that site might have been a showcase site but you still need usability and normal browser behavior that cannot be replicated out of the box, has to be implemented specifically and overall I do love HTML in such situations.

If the site had an intro animation and fancy loaders, I would definitely not have attempted doing the scroll / find  routine I do in most sites, don’t you?

However I went ahead and validated the page I made for this telecom major. A social media campaign microsite which we created in five using restful calls and jquery in the front.

Back to validation, 11 validation errors awaited me, apart from the missing “type” attributes, I had custom attributes, ouch!

I was using those attributes among others for parameters, Ajax url’s. I knew the solution was a custom DTD, I remembered from a previous oroject where we had used adobe spry widgets, the software would drop a custom namespace on top of the header. Searching on the adobe site I figured that they had a tough time too and suggested having a entity tag in the header for the valufator and remove it when going to production.

Code samples in my case are in the next post.

Oh and other than that I had a custom live chat code that had reserved keywords and unescaped characters.

So what did I do? read my next post for the answer.

1
2
3
4
5
6
7
8
9
10
11
12

	if(navigator.appName.indexOf("Explorer")== -1)
	{
 
		// Simulates the click() event for gecko based browsers
 
		HTMLElement.prototype.click = function()
		 {
			var evt = this.ownerDocument.createEvent('MouseEvents');
			evt.initMouseEvent('click', true, true, this.ownerDocument.defaultView, 1, 0, 0, 0, 0, false, false, false, false, 0, null);
			this.dispatchEvent(evt);
		 }
	}

Source : Unknown

Drop me a line and I will provide credit

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

if (document.body.__defineGetter__) {
 
       if (HTMLElement) {
 
              var element = HTMLElement.prototype;
 
              if (element.__defineGetter__) {
 
                     element.__defineGetter__("outerHTML",
 
                           function () {
 
                                  var parent = this.parentNode;
 
                                  var el = document.createElement(parent.tagName);
 
                                  el.appendChild(this);
 
                                  var shtml = el.innerHTML;
 
                                  parent.appendChild(this);
 
                                  return shtml;
 
                           }
 
                     );
 
              }
 
       }
 
}

Originial Credit : Snipplr

Step in Compressor Rater it takes the Dojo Shrinker, JSMin and YUI compressors for Javascript and produces a report as well as gives you an option to copy paste the resulting code.

More > http://compressorrater.thruhere.net/

But why now?, Mootools has just released their 1.2 version which boasts of a HashMap for clientside objects.

Jquery has seen a 1.2.1 version ( sounds familiar?, look above) for a month now.

Why dont you subscribe to the feed to be the first one to hear about it.

The CSS3 frustration continues, for e.g: the “last-child” selector, could have been a boon to site designers. The trailing “class=last” that’s added to every last item of a list, the last cell of a row could have been on the way out for once and all.

The “last-child” selector is a easy way of targeting the last element of any dom node collection. This is great for any last item of a list where you dont want that seperator to appear. MS doesn’t seem to realize that just doing half baked work with “first-child” doesn’t cut it.