Mat Kelly

Part of the logic makes this a bit tougher to resolve than originally anticipated. If a TG is detected, Mink looks to that as the source in `findTMURI()`. From there...

Badge colorization issue with 0 mementos moved to #260. Asked Drs if an aggregator ought not be queried when a URI-R specifies its own TG/TM.

1. URI-R specifies own TG @ URI-G in Link header 2. TG specifies TM @ URI-T in Link header 3. Contents @ dereferenced URI-T contain necessary information to calculate count.

There is an intermediate redirect that Mink is not catching in `createTimemapFromURI()`. https://timetravel.mementoweb.org/w3c/timegate/https://www.w3.org/TR/prov-o/ is a redirect with a Link header. Mink follows the `Location`, resulting in `TimeMap()` parsing the memento...

`fetch` can detect the redirect but only certain headers are available: ```js window.fetch(uri, {redirect: 'manual'}) .then(response => { response.headers.forEach(function(value, name) { console(name + ": " + value) // Link header...

Reverting back to XHR and sending an HTTP GET makes the header accessing. ```js var http = new window.XMLHttpRequest() http.open('HEAD', uri) http.onreadystatechange = function () { if (this.readyState === this.DONE)...

Something like the webrequest API might be able to accomplish this but it's a rabbit hole: ```js chrome.webRequest.onHeadersReceived.addListener(function (deet) { deet.responseHeaders.forEach(function (v, i, a) { if (v.name === 'Location') {...


Bumping to post-2.0.

`chrome.webNavigation.onCommitted.addListener` fires fine from mink.js, a background script, but the listener in content.js, a content script, never catches the message. The `displayUIBasedOnContext()` function reside in the content script, so message...