Roan Kattouw 74b8807df5 Resolve rendered URLs according to the provided <base> ... This is done by using the computed property value rather than the literal attribute value when rendering href and src attributes. Helpfully, this provides perfect URL resolution natively in the browser, which means the document's <base> is respected and all that good stuff. For GeneratedContentNodes, we also need to find all DOM elements inside the rendered DOM that have href or src attributes and resolve those. This is done in the new getRenderedDomElements() function, which the existing cleanup steps (remove <link>/<meta>/<style>, clone for correct document) were moved into. In order to make sure that the computed values are always computed correctly, we need to make sure that in cases where HTML strings in data-mw are parsed, they're parsed in the context of the correct document so the correct <base> is applied. We still need to solve this problem for models that actually store and edit an href or src as an attribute. I'll post more about that on bug 48915. Bug: 48915 Change-Id: Iaccb9e3fc05cd151a0f5e632c8d3bd3568735309		2013-10-28 15:16:05 +00: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
jsdifflib	Use jsdifflib for QUnit diff	2013-10-23 20:31:17 +00:00
oojs	Update oojs to v1.0.5	2013-10-23 03:16:21 +02:00
qunit
rangy
syntaxhighlight	Remove ve.getHash and use getHash from oojs instead	2013-10-22 19:14:23 +00:00
unicodejs	Fix typo (was comma instead of semicolon)	2013-08-28 11:51:52 -07:00
ve	Resolve rendered URLs according to the provided <base>	2013-10-28 15:16:05 +00:00
ve-mw	Resolve rendered URLs according to the provided <base>	2013-10-28 15:16:05 +00:00