jdlrobson 7f3be6dcd4 Do not directly manipulate the cached object ... Popups currently makes use of a render cache. Using a cache in this way without protection causes problems (I will look at cleaning this up) The hack below it `mw.popups.$popup.html( mw.popups.$popup.html() );` will lead to the html of the cached object being wiped out on IE9 meaning future loads will show an empty popup. Add a unit test (which previously would fail in IE9) to protect against this in future. Bug: T68496 Change-Id: Icef784fb389b0ab1856e2ba7464c9423ebcd62ab		2016-05-12 16:56:19 -07:00
..
ext.popups.renderer	Do not directly manipulate the cached object	2016-05-12 16:56:19 -07:00
ext.popups.core.test.js	Add test to cover mw.popups.setupTriggers	2016-04-27 19:20:27 +00:00
ext.popups.logger.test.js	Add QUnit tests for ext.popups.logger	2016-04-20 18:33:53 +00:00
ext.popups.renderer.article.test.js	Describe init method behaviour via QUnit tests	2016-05-12 16:22:59 -07:00
ext.popups.settings.test.js	Add QUnit test for ext.popups.settings	2016-04-28 16:13:20 -04:00