Hard-codes in-page links unnecessarily

[michael-n-cooper]

Respec changes in-page links to hard-coded URIs by concatenating the doc's current URI with the in-page link. E.g., <a href="#foo"> becomes <a href="http://www.example.com/myuri/#foo"> This seems unnecessary and creates a few problems. First, I stage documents from a different location than the final publication location, so the URI it inserts is wrong and has to be replaced. Second, these absolute URIs make it harder for someone to download the doc for offline reading and follow internal links easily, and similar use cases. The absolute URIs have no value-add I know of and request that in-page links be left alone.

[tobie]

Which browser are you using?

[michael-n-cooper]

Firefox 19. I didn't think that would be relevant to this behaviour or I would have included it in the bug report, as I did with some other bugs.

[tobie]

Turning relative urls into absolute ones is a known issue when using innerHTML with some versions of IE. Sounds like this isn't the issue, though.

[halindrome]

I do not see this happening either live nor when saving static versions. Can you provide a small test example?

[darobin]

@michael-n-cooper It looks like @halindrome couldn't reproduce this, and neither can I. I'm closing this issue for now; if you have an example of the behaviour please reopen with a link!