- Jan 2023
-
developer.mozilla.org developer.mozilla.org
- Dec 2022
-
w3c.github.io w3c.github.io
- Nov 2022
-
chrome.google.com chrome.google.com
-
y330.github.io y330.github.io
Tags
Annotators
URL
-
-
chromestatus.com chromestatus.com
Tags
Annotators
URL
-
-
github.com github.com
-
-
js const { generateFragment } = await import('https://unpkg.com/text-fragments-polyfill/dist/fragment-generation-utils.js'); const result = generateFragment(window.getSelection()); if (result.status === 0) { let url = `${location.origin}${location.pathname}${location.search}`; const fragment = result.fragment; const prefix = fragment.prefix ? `${encodeURIComponent(fragment.prefix)}-,` : ''; const suffix = fragment.suffix ? `,-${encodeURIComponent(fragment.suffix)}` : ''; const textStart = encodeURIComponent(fragment.textStart); const textEnd = fragment.textEnd ? `,${encodeURIComponent(fragment.textEnd)}` : ''; url += `#:~:text=${prefix}${textStart}${textEnd}${suffix}`; console.log(url); }
Tags
Annotators
URL
-
- Aug 2022
- May 2022
-
github.com github.com
-
We use the Web Annotation Protocol to sync bookmarks and last reading position across devices. At a glance it covers all the use cases here, and it's a well-defined protocol with multiple independent implementations. In particular, WAP defines a relation for discovery. Here's how we link to the annotation endpoint for a specific book in an OPDS 1.2 feed. Note the distinctive link relation and media type:
xml <link href="https://circulation.librarysimplified.org/NYNYPL/annotations/Gutenberg%20ID/40278/" type="application/ld+json; profile="http://www.w3.org/ns/anno.jsonld"" rel="http://www.w3.org/ns/oa#annotationService"/>
-
-
idpf.org idpf.org
-
A Canonical Fragment Identifier (CFI) is a similar construct to these, but expresses a location within an EPUB Publication. For example:
book.epub#epubcfi(/6/4[chap01ref]!/4[body01]/10[para05]/3:10)
Tags
Annotators
URL
-
- Apr 2022
-
datatracker.ietf.org datatracker.ietf.org
-
IMAP URL for text fragment
``` The URL: <imap://minbari.example.org/gray-council;UIDVALIDITY=385759045/; UID=20/;PARTIAL=0.1024>
may result in the following client commands and server responses:
<connect to minbari.example.org, port 143> S: * OK [CAPABILITY IMAP4rev1 STARTTLS AUTH=ANONYMOUS] Welcome C: A001 AUTHENTICATE ANONYMOUS S: + C: c2hlcmlkYW5AYmFieWxvbjUuZXhhbXBsZS5vcmc= S: A001 OK Welcome sheridan@babylon5.example.org C: A002 SELECT gray-council <client verifies the UIDVALIDITY matches> C: A003 UID FETCH 20 BODY.PEEK[]<0.1024> ```
ABNF:
abnf partial-range = number ["." nz-number] ; partial FETCH. The first number is ; the offset of the first byte, ; the second number is the length of ; the fragment.
-
-
mgearon.com mgearon.com
Tags
Annotators
URL
-
-
-
-
wicg.github.io wicg.github.io
- Aug 2021
-
stackoverflow.com stackoverflow.com
-
Th part of an URI after the # is called "fragment" and is by definition only available/processed on client side (see https://en.wikipedia.org/wiki/Fragment_identifier).
-
The main problem is that the browser won't even send a request with a fragment part. The fragment part is resolved right there in the browser. So it's reachable through JavaScript.
-
- Jun 2021
-
www.ncbi.nlm.nih.gov www.ncbi.nlm.nih.gov
-
Okazaki fragment
Can anyone explain what an Okazaki fragment is? OR link us to an online resource that helps us understand these?
-
- May 2021
-
stackoverflow.com stackoverflow.com
-
What I am attempting to do is to highlight a div with a certain id, when It has been referred to by an anchor on another page IE: User clicks link href="qw.html#test", when the page is loaded, then the div with the id="test" is highlighted so that the user can see it clearly.
-
You need to use the :target pseudo-class: :target { background-color: #ffa; }
-
-
www.impressivewebs.com www.impressivewebs.com
-
The simple problem that I see with fragment identifiers is that their existence and functionality relies completely on the developer rather than the browser. Yes, the browser needs to read and interpret the identifier and identify the matching fragment. But if the developer doesn’t include any id attributes in the HTML of the page, then there will be no identifiable fragments. Do you see why this is a problem? Whether the developer has coded identifiers into the HTML has nothing to do with whether or not the page actually has fragments. Virtually every web page has fragments. In fact, sectioning content as defined in the HTML5 spec implies as much. Every element on the page that can contain content can theoretically be categorized as a “fragment”.
at the mercy of author
-
This means that, regardless of what the developer has done behind the scenes in the HTML, all HTML fragments on that page should be identifiable by external referrers.
-
-
stackoverflow.com stackoverflow.com
-
There is a fundamental weakness in the name attribute, which the id attribute addresses: the name attribute is not required to be unique. This is OK for forms where you can have multiple elements with the same name, but unsuitable for the rest of the document where you are trying to uniquely identify an element.
-
-
simonstl.com simonstl.com
-
-
HTML fragment identifiers, as defined in the registration for the text/html media type [RFC2854] operate on id attributes and (now less frequently) the name attribute of the a, applet, frame, iframe, img and map elements.
-
-
mgearon.com mgearon.com
- May 2020
-
-
Pham, T. M., Kondor, I., Hanel, R., & Thurner, S. (2020). The effect of social balance on social fragmentation. ArXiv:2005.01815 [Nlin, Physics:Physics]. http://arxiv.org/abs/2005.01815
-
- Apr 2020
-
Local file Local file
-
The hit rate was found to be much lower thanthat of the fragment screen
the author implied that fragment screening usually has higher hit rate than drug size library screening.
-
a hit rate of about 4%
hit rate of 4% by DSF is similar to that of screening against kinase targets, interesting.
-
fragment library
fragment screening for binders are really powerful. this library contains 800 fragments
-
- Mar 2020
-
pubs.acs.org pubs.acs.org
-
covalent fragment screening
-
- Sep 2019
-
-
stackoverflow.com stackoverflow.com
-
stackoverflow.com stackoverflow.com
-
stackoverflow.com stackoverflow.com
-
developer.mozilla.org developer.mozilla.org:target1