Roan Kattouw c06a86587c Deal with Parsoid's protocol-relative <base> tags in a DOMParser world ... Protocol-relative <base> tags are fine when the iframe trick is used because the iframe inherits a default base URL from the parent document, so if the <base> is relative it can be resolved against that. However, a document created with DOMParser (or document.implementation, oops!) won't inherit anything, so anything other than a fully absolute <base> will just break. To make Parsoid's relative <base> work anyway, resolve it in the context of the main document, then write the resolved version back into the <base> tag. Change-Id: I7261bd5dbe9ec1f4077a4e5a00bd2a03ac237ca0		2014-03-26 21:56:23 -07:00
..
styles	Update VE core submodule to master (520299e)	2014-03-14 13:13:02 -07:00
targets	Merge "Add new 'vehidebetadialog' GET parameter to not show the beta dialog"	2014-03-24 23:26:39 +00:00
ve.init.mw.js	Bump copyright like it's 2014	2014-01-05 20:06:50 +08:00
ve.init.mw.LinkCache.js	Display links to nonexistent pages as red	2014-03-20 02:42:33 +00:00
ve.init.mw.Platform.js	Display links to nonexistent pages as red	2014-03-20 02:42:33 +00:00
ve.init.mw.Target.js	Deal with Parsoid's protocol-relative <base> tags in a DOMParser world	2014-03-26 21:56:23 -07:00
ve.init.mw.TargetEvents.js	Fix copyright year range for fourteen files not updated to 2011-2014	2014-03-24 18:36:51 -07:00