The suggested implementation is to add something like the following in to shortcuts.js (might want to renamed this to something more generic now - like content.js - ensuring manifest.json, background.js and Makefile are updated also);
This will listen for a request from the background page that will be triggered when the user activates a template. This request will need to wrap the build*Data functions and requires the current tab;
chrome.tabs.sendRequest(tab.id,{},function(response){// Continue to build data...});
Since I'm going to be making this request each time it's worthwhile getting the selected text at the same time (as implemented above) so users should also be able access the {selection} tag when using popup/shortcuts.
The text was updated successfully, but these errors were encountered:
As suggested by an anonymous user, I will add a tag that allows users iterate over any links in the current selection.
The suggested implementation is to add something like the following in to
shortcuts.js
(might want to renamed this to something more generic now - likecontent.js
- ensuringmanifest.json
,background.js
andMakefile
are updated also);This will listen for a request from the background page that will be triggered when the user activates a template. This request will need to wrap the build*Data functions and requires the current tab;
Since I'm going to be making this request each time it's worthwhile getting the selected text at the same time (as implemented above) so users should also be able access the
{selection}
tag when using popup/shortcuts.The text was updated successfully, but these errors were encountered: