Add a general fragment identifier handler #5599
The interpretation of a fragment identifier - the last part of an URL, introduced by a hash mark - depends on the mimetype of the documents the URL points to.
The fragment of
At moment jupyterlab is able to handle only HTML fragment idenfiers.
So we should add a more general mechanism to deal with fragment identifiers.
A possible design is this.
If there is agreement on that design I can submit a PR.
The text was updated successfully, but these errors were encountered:
I think this is a nice idea @AlbertHilb. My main concern is that I don't think we should rely too much on undocumented, un-spec'ed behavior in various mimetypes. For instance, the
I think your overall strategy sounds reasonable, but I'd like to hew as closely as possible to open standards as possible.
Looks like I was off base about PDF fragments: they are described in the IETF documentation: https://tools.ietf.org/html/rfc8118#page-3
See also CSV: https://tools.ietf.org/html/rfc7111
So, I think this is a great idea @AlbertHilb! Your first idea of