- Jul 2023
-
thesephist.com thesephist.com
Tags
Annotators
URL
-
- Jan 2023
-
developer.mozilla.org developer.mozilla.org
- Dec 2022
-
www.w3.org www.w3.org
Tags
Annotators
URL
-
-
gist.github.com gist.github.com
- Nov 2022
-
-
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
-
-
stackoverflow.com stackoverflow.com
-
p10ns11y.github.io p10ns11y.github.io
-
github.com github.com
-
unprogrammer.com unprogrammer.com
-
bvaughn.github.io bvaughn.github.io
-
codepen.io codepen.io
Tags
Annotators
URL
-
-
twitter.com twitter.com
-
www.w3.org www.w3.org
Tags
Annotators
URL
-
-
microsoftedge.github.io microsoftedge.github.io
-
www.azabani.com www.azabani.com
-
```html
<style> ::selection { background: #00FF00; } ::highlight(foo) { background: #FF00FF; } </style> <script> getSelection().removeAllRanges(); getSelection().selectAllChildren(document.body); const style = getComputedStyle(document.body, "::highlight(foo)"); console.log(style.backgroundColor); </script> <body>Hello, world!</body>```
-
- Aug 2022
-
web.hypothes.is web.hypothes.is
-
-
In line with the much-requested (and long-longed-for) feature of highlights in different colors (an exhaustive list given in #198), I would like to suggest allowing (automatic) coloring of highlights based on tags with designated patterns (like code:critiques, code:non-ergodicity in psychology, etc.), or alternatively, all tags (i.e., without specific patterns).
-
-
-
Made a quick strawman mockup of what it could look like from the editor side:
-
-
annotator.apache.org annotator.apache.org
Tags
Annotators
URL
-
-
developer.mozilla.org developer.mozilla.org
-
chromestatus.com chromestatus.com
- Jan 2022
-
github.com github.com
-
i implemented this myself this way:
code syntax highlighting: pasted both his highlighted version (as an image) and unhighlighted version (as text, so that it can be copied/pasted, indexed, whatever)
-
- Apr 2021
-
1tomission.omeka.net 1tomission.omeka.net
-
On the road again...
Although we're using an Omeka Simple Page as our start page, the link I'm using points us to the first page of the Exhibit.
-
- Aug 2020
-
web.hypothes.is web.hypothes.is
-
but there are no comments or tags
Is this not a comment on a highlight? And did I not just add tags? Is this article out of date?
-
- Oct 2019
-
github.com github.com
- May 2019
-
journal.disruptivemedia.org.uk journal.disruptivemedia.org.uk
-
implicit social contract
To what extent does the fact that Hypothesis annotations show up in our feeds (and are thus useful for us tracking our movement through texts) while mere highlights do not, determine usage patterns ?
-
- Apr 2017
-
www.colorado.edu www.colorado.edu
- Sep 2015
- Feb 2014
-
www.lexisnexis.com www.lexisnexis.com
-
Why highlight? Like annotating, highlighting may seem unimportant if you create thorough, well-constructed briefs, but highlighting directly helps you to brief. It makes cases, especially the more complicated ones, easy to digest, review and use to extract information. Highlighting takes advantage of colors to provide a uniquely effective method for reviewing and referencing a case. If you prefer a visual approach to learning, you may find highlighting to be a very effective tool.
Why highlight?
-
