3 ms·
in this case it looked OK > Though existing HTML support for id and name attributes specifies the target element directly in the fragment, most other mime type
by est 8y ago
in this case it looked OK
> Though existing HTML support for id and name attributes specifies the target element directly in the fragment, most other mime types make use of this x=y pattern in the fragment, such as Media Fragments (e.g. #track=audio&t=10,20), PDF (e.g. #page=12) or CSV (e.g. #row=4).
fragments is already there but most pages do not have a clickable ID attribute. If Chrome could automatically provide one I think it's more convenient than F12 a devtool for links.
- pjmlp 8y agoIE 5 was also welcomed with joy when it arrived.
- peteretep 8y ago> in this case it looked OK That’s not really the point
- gammateam 8y agoI’m fine skiing down this slippery slope
- detaro 8y agoAlthough there already was a proposed standard by a W3C group for doing this, although it is a lot more complicated (with a bunch of variations, but even implementing one of those would be nice): https://www.w3.org/TR/selectors-states/#json-examples-converted-to-fragment-identifiers https://www.w3.org/TR/selectors-states/#json-examples-conver...