Curtis Wilcox on Nostr: nprofile1q…e6h3y Safari has supported text fragment URLs for a couple of years. I ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqzylk3x2cvl79r854gtnqjvh7cjns6zzynvf39llvfvh6gl89cgvsre6h3y (nprofile…6h3y)
Safari has supported text fragment URLs for a couple of years. I think what the MDN page is saying is Safari doesn't support `document.fragmentDirective`, used to detect whether a browser supports text fragments.
However, unlike Chrome and Firefox (and unlike the behavior with document fragments), Safari does not change where focus moves when you press Tab after using a text fragment. When you use a text fragment in other browsers then press Tab, focus is moved to the next focusable element after the fragment. But when you use a text fragment in Safari then press Tab, focus moves to the first focusable element in the *document*, (the window scrolls to move the focused element into view).
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqyx409e8cvsfzju9gf3jky7aeyadyeqhxr9r0nqpv3pyele0eku9q54zrnw (nprofile…zrnw)
Safari has supported text fragment URLs for a couple of years. I think what the MDN page is saying is Safari doesn't support `document.fragmentDirective`, used to detect whether a browser supports text fragments.
However, unlike Chrome and Firefox (and unlike the behavior with document fragments), Safari does not change where focus moves when you press Tab after using a text fragment. When you use a text fragment in other browsers then press Tab, focus is moved to the next focusable element after the fragment. But when you use a text fragment in Safari then press Tab, focus moves to the first focusable element in the *document*, (the window scrolls to move the focused element into view).
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqyx409e8cvsfzju9gf3jky7aeyadyeqhxr9r0nqpv3pyele0eku9q54zrnw (nprofile…zrnw)