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
..
nodes	Prevent escaping of piped links in wikitext parameters	2013-07-11 16:20:39 +01:00
ve.dm.InternalList.test.js	Prevent naming collisions when generating unique reference names	2013-09-19 21:03:15 -07:00
ve.dm.MWConverter.test.js	ve.copy: Remove obsolete copyArray and copyObject	2013-07-30 01:44:22 +02:00
ve.dm.mwExample.js	Resolve rendered URLs according to the provided <base>	2013-10-28 15:16:05 +00:00
ve.dm.SurfaceFragment.test.js	Actually run all the tests	2013-07-10 19:36:55 -07:00
ve.dm.Transaction.test.js	Remove ve.getHash and use getHash from oojs instead	2013-10-22 19:14:23 +00:00