Changes between Version 12 and Version 13 of Ticket #4101


Ignore:
Timestamp:
07/29/2016 09:10:24 AM (4 years ago)
Author:
kzar
Comment:

Yep, that was the problem. The MutationObserver was triggering itself. (Apparently with older versions of Chrome element.style.setProperty is enough to trigger a MutationObserver even if the new value is the same as the old one...)

Legend:

Unmodified
Added
Removed
Modified