You need to
before you can comment on or make changes to this bug.
1. Open the URL.
2. If under "Log:" it does not say 3, 2 the test has failed.
(The version and OS and such are all wrong, as I'm using Opera on Ubuntu at the moment...)
Confirmed and even extended with this testcase.
Created an attachment (id=24560) [details]
Easier (imo) to understand testcase
Created an attachment (id=24570) [details]
I'm a little worried about the performance implications of this, but not sure how the best way to test would be.
(From update of attachment 24570 [details])
Landed in r37800. As a workaround for versions that still have this bug, you can force an update by setting just about any non-class property when you set the class.
*** Bug 22523 has been marked as a duplicate of this bug. ***