A workaround that's worked well for me is to nest the Table of Contents macro within the Expand macro.  No funky linking necessary, just the caveat of an additional click to see the ToC.  

Ditto to Paul's comment. It's frustrating that things like this come up with an otherwise first-rate product. I have to hear my chief documenter say things like, "We should switch to Sharepoint."

I'm experiencing this with Confluence 5.8.9, too, so near as I can tell, this problem has existed in every version. I can't seem to get the workaround to work, either.

I'm voting for this.

One of the purposes of having a TOC is to give clickable links to further down the page, and yet this breaks the HTML anchors!

It's actually quite frustrating, and would be comical if it was some random free program I found on the internet!

Also just wanted to say that one of the joys of using Confluence[1] is the way that links usually update themselves when a page is renamed. It makes me sad that I either have to:

1. remove the TOC from a page OR
2. use a full URL in a link, knowing that it will undoubtedly be broken at some point in the future (pages get renamed, headings get altered)

[1] Confluence is a fine product, even though I'm well-known for leaving grumpy comments about it. I like it really.

I think this has always been an issue, but I've only just found this bug report. I've been using Confluence since version 3.x.

Anchors work fine for me when linking from one place to another place on the same page, but I've never been able to get an anchor to work from one page to another, and now I see that's because of the {toc} macro.

It's now 2016, and it's still broken.

And I find it a bit frustrating that the documentation encourages the use of {toc}, when this anchor issue has existed since the dawn of time.

"Table of contents on page: Consider using the Table of Contents Macro to generate a list of links pointing to the headings on the page. The list of links will appear on the page, and will be automatically updated each time someone changes the wording of a heading."

I think we are seeing the same issue in 5.4.4. When you enter the full URL (including anchor) into your browser, does it first navigate to the anchor for a split second, but then automatically scroll back to the top?

Sorry, that's not quite right - that's only if your anchors always have the same name as the heading (which ours do).

Using "Heading name", and "Anchor name", the workaround link is

Page name#Anchor nameHeading Name

We've just come across this. There is a workaround, which is repeating the anchor name in the link. For example, if previously you would have linked to

Page name#Anchor name

instead link to

Page name#Anchor nameAnchor name

to go to the correct anchor on the page.