Fix for custom BreezeWiki host script registration
Need to use absolute paths, and run at document_idle to capture elements that are injected after initial page loadpull/680/head
parent
5ee5fc9123
commit
6ad9c25cb2
|
@ -572,8 +572,8 @@ document.addEventListener('DOMContentLoaded', () => {
|
||||||
chrome.scripting.registerContentScripts([{
|
chrome.scripting.registerContentScripts([{
|
||||||
id: 'content-banners',
|
id: 'content-banners',
|
||||||
matches: [breezewikiCustomDomain + '/*'],
|
matches: [breezewikiCustomDomain + '/*'],
|
||||||
js: ['scripts/content-banners.js'],
|
js: ['/scripts/common-functions.js', '/scripts/content-banners.js', '/scripts/content-breezewiki.js'],
|
||||||
runAt: "document_start"
|
runAt: "document_idle"
|
||||||
}]);
|
}]);
|
||||||
chrome.storage.sync.set({ 'breezewikiCustomHost': breezewikiCustomDomain });
|
chrome.storage.sync.set({ 'breezewikiCustomHost': breezewikiCustomDomain });
|
||||||
document.getElementById('breezewikiCustomHostStatus').innerText = 'Successfully added';
|
document.getElementById('breezewikiCustomHostStatus').innerText = 'Successfully added';
|
||||||
|
|
Loading…
Reference in New Issue