In #2567, I had to split information regarding the three shape detection APIs between two locations in the document. I provided links between the locations so that readers could easily move between them. When I placed the target anchors in locations that seemed logical from a code standpoint I found that following the links lead to a page view where the linked-to content is scrolled off the top of the page.
For example, I placed an anchor in the Shape Detection label under "Behind a flag" and linked to it from elsewhere in the document. When I followed that link, I was brought to a view that looked like this:
What I expect to see is this:
I tried several anchor placements that seemed logical from a code standpoint. None of them produced the outcome I wanted. The only thing that seemed to work was placing the anchors in illogical locations: the end of the introductory paragraph, for example. This is hacky but I accepted the approach because the linking is temporary. As soon as all three portions of the Shape Detection API are enabled by default, the links will go away.
I am under the impression that there are techniques for addressing this that are less hacky, but I'm not familiar with them. Since they may involve changing site code and not something I can implement as an author, I've opened this ticket.
In #2567, I had to split information regarding the three shape detection APIs between two locations in the document. I provided links between the locations so that readers could easily move between them. When I placed the target anchors in locations that seemed logical from a code standpoint I found that following the links lead to a page view where the linked-to content is scrolled off the top of the page.
For example, I placed an anchor in the Shape Detection label under "Behind a flag" and linked to it from elsewhere in the document. When I followed that link, I was brought to a view that looked like this:
What I expect to see is this:
I tried several anchor placements that seemed logical from a code standpoint. None of them produced the outcome I wanted. The only thing that seemed to work was placing the anchors in illogical locations: the end of the introductory paragraph, for example. This is hacky but I accepted the approach because the linking is temporary. As soon as all three portions of the Shape Detection API are enabled by default, the links will go away.
I am under the impression that there are techniques for addressing this that are less hacky, but I'm not familiar with them. Since they may involve changing site code and not something I can implement as an author, I've opened this ticket.