Comments on: Ajax Cookbook: Helpful JavaScript tips http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips Cleaning up the web with Ajax Wed, 17 Mar 2010 19:36:37 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Sam Hennessy http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips/comment-page-1#comment-245387 Sam Hennessy Tue, 19 Dec 2006 15:42:22 +0000 http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips#comment-245387 Ron, there are always exceptions, but most of the time changing right click behavior it a bad usability choice. Ron, there are always exceptions, but most of the time changing right click behavior it a bad usability choice.

]]> By: Ron http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips/comment-page-1#comment-245330 Ron Mon, 18 Dec 2006 11:58:53 +0000 http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips#comment-245330 Laurent, actually, there are some instances where disabling the browser's context menu is useful. For instance, if you are building a browser based application, where you want to use the right click to show your own context menu, which might make more sense to the user than the browser's menu. At my work, we're using it in our CMS, and I've never heard any complaints about it. Laurent, actually, there are some instances where disabling the browser’s context menu is useful. For instance, if you are building a browser based application, where you want to use the right click to show your own context menu, which might make more sense to the user than the browser’s menu. At my work, we’re using it in our CMS, and I’ve never heard any complaints about it.

]]> By: Kris Zyp http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips/comment-page-1#comment-245314 Kris Zyp Sun, 17 Dec 2006 07:26:03 +0000 http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips#comment-245314 Laurent, excellent commentary and corrections, your optimizations are indeed much better than Bret's. Laurent, excellent commentary and corrections, your optimizations are indeed much better than Bret’s.

]]> By: Laurent http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips/comment-page-1#comment-245311 Laurent Sun, 17 Dec 2006 02:13:10 +0000 http://ajaxian.com/archives/ajax-cookbook-helpful-javascript-tips#comment-245311 bahh, why would he obviOusly know anything better ? because he worked on the first google maps, that's far to be a reference to me. The 4 ONLY examples are far to be disabling context menu FF1.5,FF2, Opera8.52,Opera9 = no effect, considering to change the default behavior of the right mouse button is a big UI mistake. Dont consider it. Ever. debug log document.write, window.open, awfull tips, dont consider using it cancel events 2 tests for each functions for EVERY cancel, no optimization at all, dont use it cross browser events nothing new exposed, it has been better explained a lot all over the web, once again there is NO optimization at all, no way to control the execution scope, no way to choose between DOM0 and DOM2 registration, no way to add an arbitrary object to the listener. Very bad point, you have to keep the reference to the registered listener if you want to remove it before the document unload. Dont use it, better look for a robust addEvent(), it's easy to found, it was all over the web 6 months ago. Let's hope it will get any better in the future, but it looks like a dead horse giving deprecated tips with bad code practice, i doubt it to be of any use. bahh, why would he obviOusly know anything better ? because he worked on the first google maps, that’s far to be a reference to me. The 4 ONLY examples are far to be

disabling context menu
FF1.5,FF2, Opera8.52,Opera9 = no effect, considering to change the default behavior of the right mouse button is a big UI mistake. Dont consider it. Ever.

debug log
document.write, window.open, awfull tips, dont consider using it

cancel events
2 tests for each functions for EVERY cancel, no optimization at all, dont use it

cross browser events
nothing new exposed, it has been better explained a lot all over the web, once again there is NO optimization at all, no way to control the execution scope, no way to choose between DOM0 and DOM2 registration, no way to add an arbitrary object to the listener. Very bad point, you have to keep the reference to the registered listener if you want to remove it before the document unload. Dont use it, better look for a robust addEvent(), it’s easy to found, it was all over the web 6 months ago.

Let’s hope it will get any better in the future, but it looks like a dead horse giving deprecated tips with bad code practice, i doubt it to be of any use.

]]>