+1 not being able to link to headers on long READMEs is very frustrating. I'm surprised the parser can't just create an id for headers. This issue needs to be re-opened. I'd commit a patch to make this work if it knew where to or even if I could?
Yes, John is right on! This cannot be considered true markdown as long as the consumer must know internal implementation details of bitbucket's parser. The purpose of MarkDown/CommonMark is to be universal! Continuing on the stubborn path of keeping the link generation logic unique just fractures the community.
Is the resolution portable to other system's that render markdown. Prefixing with 'markdown-header' seems highly annoying if not. Just started attempting to use your wiki feature and this seems to be a deal breaker for me.
Throwing my two cents in.
I'd been toying with trying to document my office's workflow in markdown, adding relevant reference/anchor links to assist in navigation and integration.
Not supporting the features that are claimed to work (even showcasing them not working) is a major misstep.
This is a blocker as someone who's trying to use this in an enterprise environment.