c69's Browser Pit

played around with gradients today...
Disclaimer: Do not use in production. Nothing of this works in Chrome (because they have not uprefixed gradients, just yet)

Pure CSS Triangle: http://jsfiddle.net/GBjXp/
Boring, just another triangle.

Simple color mix: http://jsfiddle.net/ugPUu/
Boring, RGB colors @ 120 degree shift.

Eye in a Tube: http://jsfiddle.net/qAYbK/
Overlaying radial gradients.
Notice how Firefox is starting to experience troubles with this one - dirty colors, stuttering. Special: drag/resize jsfiddle's layout grid, and you will see how Firefox draws radial-gradient all over your screen.

Liquid sky: http://jsfiddle.net/8Q8dj/
Something more visually enoyable.
This one is using background-size to patternize gradient, small alpha hsla for spiral gradient, also, corners are bluntly hacked.
Looks as intended in ie10/o12, but FF19 adds extra psychedelic effects, which you might decide to enjoy

this is the bug of IE8:
http://webbugtrack.blogspot.com/2008/01/bug-263-beware-of-doubleclick-in-ie.html

never rely on semi-colon insertion! (unless you like to spend friday evenings hunting bugs, while your colleagues are having fun).

Everybody knows, that:

return 
{
x: 1
} 

will return undefined, because semicolon will be inserted right after return.

But there are few other illustrative examples (all will throw exceptions):
-1.----

var foo = 'asdf'
[1,2,3].forEach(function(value){console.log(value)})

'asdf'[1,2,3] is syntax error

-2.----

var foo = 1+2
('asdf' + 'blubb').toUpperCase()

'2' is not a function

-3.----
This code will work:

function(){}

(function(){
})()

But this one:

var foo = function(){}

(function(){
})()

will throw:

'}
(function(){
})' is not a function 

-------
copy/pasted from comment in "grumpy old farts vs dumb emo kids"* thread : https://github.com/twitter/bootstrap/issues/3057#issuecomment-5140311
-------
via: http://brendaneich.com/2012/04/the-infernal-semicolon/
-------
p.s.: * - 'seasoned veterans vs creative youth' would be less offensive, but.. can i at least insult people, more talented than me, if i cant write better code ?

Compilation was a success!
Original Size:	1.06KB (886 bytes gzipped)
Compiled Size:	1.83KB (861 bytes gzipped)
Saved -72.70% off the original size (2.82% off the gzipped size)

agressive inlining that Closure Compiler does - can produce funny results, like doubling your code size Because it transforms
var a = 's'; var b = 'z' + a; var c = a;
to
var b = 'zs';
var c = 's';
and if 's' was base64-url.. you can imagine result.

Read more...

http://functionsource.com/post/john-j-barton-and-the-future-of-firebug

Now all of the browsers have (or will soon have) their own debuggers. Basing next gen work on Firebug is not practical. The pace of change in browsers is too fast for our team size. Firebug hasn’t really been able to keep up with Firefox, let alone compete with other tools. Moreover, the shift from desktop to mobile and from one high-tech browser (Firefox) to three or more requires additional development effort. I think our current drive to re-architect Firebug is on the right track, but I could not obtain another year of support from IBM to contribute to that work.

Things don't look good for Firefox, with a lot of key visionaries leaving Mozilla over the last 6 months ... Yet, from the other point - WebKit might [already] be "a new Gecko", with fanboys, google, "hackers" and 3rd party devs (like Adobe) pumping out tonnes of code for it.