Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nifty feature, but what the heck were they thinking with a delimiter like `:~:` for Fragment Directives? Were they drunk?

Why not just a second Hash # character?

With a Fragment and Directive specified, hence separated # marks:
HTML:
/some/webpage#SomeHeading#text=something

With only a Directive specified, hence the double-#.
HTML:
/some/webpage##text=something

Developers are just making coding much more complicated than it needs to be!
 
Developers are just making coding much more complicated than it needs to be!
I don’t understand. This isn’t something that a developer would need to interact with, aside from browser developers, because it’s done entirely on/by the client browser.

Aside from that and in defense of the developers, this was something that was standardized by W3C.
 
Wow! Didn‘t know that feature! Works on iphone and ipad too. :)
Thanks.
 
I ran into this because of someone sending me this for their web site as a link and was like "what is this?" But it doesn't work on older browsers, so can be frustrating when sharing with a person who has to use an older browser. I still didn't know it was an official standard until this post though.
 
Anchors are server-side and created before you see the page. This is something that you can use to identify a particular chunk of text in a web page on an ad hoc basis.

I just discovered Brave browser has this feature its called copy link to highlight. Here is example from this page:

 
I followed your link on my iPad A16, and it brought me back to your comment. When I scrolled up the page I found the text from your link, highlighted as it was supposed to be. It seems odd that Safari didn’t scroll to that text. Maybe a bug? 🤷‍♂️
 
I followed your link on my iPad A16, and it brought me back to your comment. When I scrolled up the page I found the text from your link, highlighted as it was supposed to be. It seems odd that Safari didn’t scroll to that text. Maybe a bug? 🤷‍♂️

I just realised this "brave browser" feature is actually the same Google implementation of sharing the text and the one that safari should implement according to the article but you have to have safari 18.2.

I think something is wrong with my original link. I tried it again with this one. It workedo n Brave, safari 17, and vivaldi:
 
I just realised this "brave browser" feature is actually the same Google implementation of sharing the text and the one that safari should implement according to the article but you have to have safari 18.2.

I think something is wrong with my original link. I tried it again with this one. It workedo n Brave, safari 17, and vivaldi:
Yes, this second link works perfectly 👍
 
I just realised this "brave browser" feature is actually the same Google implementation of sharing the text and the one that safari should implement according to the article but you have to have safari 18.2.

I think something is wrong with my original link. I tried it again with this one. It workedo n Brave, safari 17, and vivaldi:
For anyone reading this in the future, you don't need Safari 18.2, Safari 17.6 works fine with it (maybe Safari 16 too?). I am using 17.6 right now.

Your first link brought me straight to my own comment above with no highlighting but the second one worked fine.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.