DOM events in the Microsoft AJAX Library

re: DOM events in the Microsoft AJAX Library

Bertrand Le Roy — Tue, 17 Jun 2008 16:26:02 GMT

@Lokas: you need to define testTable, for example var testTable = $get("testTable");. You also need to use square brackets instead of parentheses to get the rows: testTable.rows[i].

re: DOM events in the Microsoft AJAX Library

Lokas — Tue, 17 Jun 2008 04:16:41 GMT

Well I have started to play little bit with the ATLAS and I want to add DOM event handler to TR element.

Code works fine for IE , but in a firefox load event is happend , but events are not hooked to dom element ...

I'm using asp 2.0 , please give me a tip , relly dont have a clue what is going on......

function pageLoad()

{

alert('atload');

for(var i = 0 ; i<testTable.rows.length;i++)

$addHandler(testTable.rows(i),"click",RowClick);

}

function RowClick(e)

{

alert(this.innerHTML);

}

re: DOM events in the Microsoft AJAX Library

Bertrand Le Roy — Fri, 09 Nov 2007 19:23:58 GMT

Dave: If I'm not mistaken, that jQuery feature appeared after that comment was written. It is true that jQuery does an excellent job at keeping to its namespace, as does Dojo.

re: DOM events in the Microsoft AJAX Library

Dave — Fri, 09 Nov 2007 15:08:01 GMT

> "It seems like we're the only ones to actually care about not colliding with existing aliases from competing frameworks, and we don't even get some credit for that?"

Actually, jQuery does a very good job of preventing namespace collisions; it only uses "jQuery" in the global namespace and you can tell it to not use "$" if someone else is using it.

docs.jquery.com/Using_jQuery_with_Other_Libraries

Microsoft Ajax events - part 1: subscribing

Atlas and more — Thu, 17 May 2007 00:20:45 GMT

When building Ajax applications, you basically deal with two kinds of events. First, there are DOM events

re: DOM events in the Microsoft AJAX Library

Bertrand Le Roy — Sat, 07 Apr 2007 17:51:46 GMT

Peter: yes, absolutely. I'll try to get that done next week.

re: DOM events in the Microsoft AJAX Library

PeterG — Sat, 07 Apr 2007 16:03:50 GMT

Are you still planning to do a post about Class events or can you point me at a good resource?

re: DOM events in the Microsoft AJAX Library

Bertrand Le Roy — Wed, 07 Mar 2007 19:22:11 GMT

Stephen: yes, potentially, unobtrusively adding events like described here enable you to build a web page that could work without JavaScript. It requires some care but it absolutely can be done and it is the direction more and more people are taking. But to be perfectly clear, it doesn't "make Ajax work" if JavaScript is off, it makes the page work reasonably if it's off. By definition, Ajax only works with JavaScript on.

I don't understand your question though. What idea are you referring to? What is not going as well as I had hoped?

re: DOM events in the Microsoft AJAX Library

Stephen Oesterreicher — Wed, 07 Mar 2007 19:09:03 GMT

Is what your doing is making AJAX work even if the browser has JavaScript turned off? It looks like it is not going as well as you had hoped. Does that mean that your idea is not going to make it out here in the real world?

re: DOM events in the Microsoft AJAX Library

Bertrand Le Roy — Wed, 06 Dec 2006 21:41:26 GMT

Jacques: the problem is that it would be very complex to subscribe to the unload event of all windows you attached events in and dispose of them properly. We just couldn't ensure the level of functionality that we can ensure in the same window.

If you're using an iframe, what I recommend is that it has its own copy of the AJAX library and pretty much works in isolation, with just the level of communication you need between JavaScript components (which you can achieve by exchanging delegates between components in different windows. Avoid DOM-based communication like you're trying because that will be a nightmare to clean up and avoid memory leaks. If you are using an iframe, that's usually because you want the iframe to be able to post and navigate independantly, which means that the dispose logic will need to be taken care of. That will be a lot easier with the iframe working as a full page, with its own copy of the framework.