Changes between Initial Version and Version 1 of Ticket #1727


Ignore:
Timestamp:
03/28/18 22:13:44 (16 months ago)
Author:
gogo
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1727 – Description

    initial v1  
    1515then expandRealtiveURls (in either incarnation) would mess with that URL in a way you didn't want probably. 
    1616 
    17 As a stop-gap fix changeset to be committed 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. 
     17As 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. 
    1818 
    1919A 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.