Allow select archives/interfaces to access Mink info using Chrome API #203
Labels
Milestone
Comments
|
Branch issue-203 has been setup with hooks. A simple web page like the following will invoke a callee's functionality in Mink: <html>
<body>
<script>
var minkId = "ehlefgjpcinhloogfldmkojonnjpnloo";
chrome.runtime.sendMessage(minkId, {"test": "case!"},
function(response) {
if (!response.success)
handleError(url);
});
</script>
</body>
</html> |
|
@weiglemc @phonedude Per above, web pages and other extensions can communicate to Chrome extensions (i.e., Mink) through message passing. Can you imagine some specific use cases for this? |
|
See also machawk1/wail#542 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using
externally_connectable( https://developer.chrome.com/extensions/manifest/externally_connectable ), an archive's webUI (or any arbitrary web page, even one on localhost) could be added to the select set of archives aggregated on-the-fly or other webpages (e.g., The Heritrix/Wayback web interfaces in WAIL) could communicate with Mink directly. This might be useful to add buttons onto the archive's web interfaces using content page manipulation.The text was updated successfully, but these errors were encountered: