Roan Kattouw 3f5486a43f Use a sane recursion guard in ve.ui.Context.prototype.hide() ... The previous recursion "guard" relied on the recursion to occur for the function to work correctly, which was very confusing. Additionally, it didn't actually work: if the inspector's onClose handler changed the selection (which is common), .hide() would recurse and the recursion guard didn't catch this (inspector wasn't undefined yet). Fortunately all that did was call .close() on the inspector again, which was caught by .close()'s own recursion guard. Instead, simply use this.hiding as a recursion guard, and refactor the function so it doesn't do two different things depending on whether it's expecting recursion or not. Change-Id: I09eb9229530468ee319ca53b730784a3f632375d		2013-10-21 14:10:23 +02:00
..
jquery	jquery.client: Update to upstream from 92f06b4a in mediawiki/core.git	2013-07-10 23:23:11 +02:00
jquery.uls	Language Inspector UI	2013-07-29 00:38:59 -04:00
oojs	oojs: Update to upstream v1.0.2	2013-07-25 17:57:41 +00:00
qunit
rangy
syntaxhighlight	Remove ve.{inheritClass,mixinClass} and use OO instead	2013-10-18 18:58:08 +02:00
unicodejs	Fix typo (was comma instead of semicolon)	2013-08-28 11:51:52 -07:00
ve	Use a sane recursion guard in ve.ui.Context.prototype.hide()	2013-10-21 14:10:23 +02:00
ve-mw	Remove ve.{inheritClass,mixinClass} and use OO instead	2013-10-18 18:58:08 +02:00