Context Navigation

Changes between Version 1 and Version 2 of Ticket #1727

v1	v2
15	15	then expandRealtiveURls (in either incarnation) would mess with that URL in a way you didn't want probably.
16	16
17		As a stop-gap fix changeset:1433 ~~next~~ will prevent by default the expansion of URLs which start with something that's not parental or self-referential. That is to say, "foo/bar.html" will not be touched, but "../foo/bar.html" will be touched, absolute urls including such a parental or self referential component, like "/foo/../bar.html, will also not be touched.
	17	As a stop-gap fix changeset:1433 will prevent by default the expansion of URLs which start with something that's not parental or self-referential. That is to say, "foo/bar.html" will not be touched, but "../foo/bar.html" will be touched, absolute urls including such a parental or self referential component, like "/foo/../bar.html, will also not be touched.
18	18
19	19	A better fix long-term would be I think to expand relative URLs incoming to the document url (`baseHref`) (in `inwardHTML`) and expand relative URs outgoing (in `outwardHTML`) to the file including Xinha, and also have an option to "contract" (opposite of expand) semi-absolute urls to be relative to the document url. Effectively, we need two different operations for `fixRelativeLinks` one for incoming and one for outgoing.