Comments on: IE 8 beta 2 Ajax features

By: TNO

TNO — Sat, 11 Oct 2008 03:54:57 +0000

Refer to the DOM level 3 events.

By: Jeria

Jeria — Wed, 08 Oct 2008 07:41:50 +0000

How come that they add HTML 5 features but completely ignore the DOM Level 2 Events Specification that is a recommendation since 2000?

http://www.w3.org/TR/DOM-Level-2-Events/

Sad that we still have to deal with the crappy attachEvent.

By: Jordan

Jordan — Wed, 08 Oct 2008 07:10:54 +0000

@eyelidlessness:
Getting MS to implement any change is harder than scoring with Paris. And not only that, you’ll also have to convince Mozilla, Opera and Apple to implement that too or else it would be useless. Alternatively you could convince the Ajax libraries to implement that, which would probably be easier, but doesn’t really achieve the purpose of absolute universal adoption. Or in the very least you could ask end-developers to implement that, which kind of defeats the purpose of helping others, when in reality you are only asking them to help themselves.

By: eyelidlessness

eyelidlessness — Wed, 08 Oct 2008 02:41:13 +0000

Storage.prototype.get = Storage.prototype.getItem;
Storage.prototype.set = Storage.prototype.setItem;

Is that so hard?

By: Aimos

Aimos — Tue, 07 Oct 2008 19:53:45 +0000

May be it’s a bit late for last changes to the HTML5 specs, but why the hell ist it storage.setItem and storage.getItem.

According to http://www.whatwg.org/specs/web-apps/current-work/#storage-0 a storage interface has only a few methods, setItem, getItem, clear, key(n), removeItem() and length().

I would keep it simple rename .setItem in .set, .getItem in .get() and removeItem() in remove().

sessionStore.set(‘foo’, ‘bar’); looks for me more usable, like sessionStore.setItem(‘foo’, ‘bar’); with the setItem() method I think there are more types of setX methods available. Maybe setObject, setArray, setReference and so forth, but I *think* you can store everything with just setItem() by now.

By: JonnyBlazed

JonnyBlazed — Tue, 07 Oct 2008 17:51:27 +0000

correct me if im wrong, but isn’t this being implemented in almost the exact same way in HTML5?

i understand the benefit if it means you’ll be able to eliminate the use of iFrames entirely, but what good is that to developers if it’s IE only? we’re just going to have to build the iFrame in anyways to be cross-browser compatible…