Bug with Chrome's localStorage implementation?

Question

Further to this question, I\'m getting a curious result when binding a function to the change event of the Storage object in Chrome 8.0.552.224.

The test:

Answer 1

Ivo Wetzel's answer for what is going wrong is correct.

I was having the same problem but managed to work around this limitation in the spec by manually creating and firing a StorageEvent in the tab that initiated the storage change (see StorageEvent#initStorageEvent).