Issue Description
There are no “sub-links” for each property on this page, creating difficult navigation to the desired property as well as the impossibility to send a direct link of that property to anyone.
Issue Area: DevHub Content
Page URL: StarterGui | Roblox Creator Documentation
I don’t believe any other part of the dev hub has this so it may be hard to implement.
However they do not have links that you can give out to automatically scroll to that part.
However this is for functions in where there are none in this article.
I think you understand my suggestion. We’ll leave it to the Roblox team to judge whether this request is pertinent.
I would like to bump this issue as this is very troubling when trying to link documentation to those that need it. Due to how the pages are constructed, # anchor links simply do not work as they should. For the same reason, :~:=text links also do not work. This wasn’t an issue in the past.
Please look into this when possible, thank you.
With the link provided in this post I can confirm this is not an active issue as the page scrolled to the correct SetCore documentation.
link I used:
https://create.roblox.com/docs/reference/engine/classes/StarterGui#SetCore
This does not occur for me on many pages. It does in that specific case, but not in others.
For example:
https://create.roblox.com/docs/reference/engine/classes/Player#Character
It may also be that it works sometimes, but not other times. The page doesn’t always load quickly. I’m also using Firefox, if that matters.
hm that’s interesting because that link seems to work for me too?
however i am using brave (chromium based) and you’re using firefox which is its own thing so maybe that could be the issue
I got the character link to work 3 times out of 10 times, so I think it really is a consistency issue, perhaps to do with Firefox.
My theory is that it gives up the anchor point if the page doesn’t load in a certain length of time, but I couldn’t say for sure. It does seem to do it more consistently if I load that part of the page first and then open a new page to that link, which puts it in cache, which would then make it load faster for the anchor to work. But again, I can’t say for sure.
I just tried loading the link on a slow VPN and it worked every time so it seems to be a browser specific issue.
I can confirm that it works every time on Chrome, so I think you are correct.
