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 load
pull/680/head
Kevin Payravi 2024-02-23 02:27:53 -05:00
parent 5ee5fc9123
commit 6ad9c25cb2
1 changed files with 2 additions and 2 deletions

View File

@ -572,8 +572,8 @@ document.addEventListener('DOMContentLoaded', () => {
chrome.scripting.registerContentScripts([{
id: 'content-banners',
matches: [breezewikiCustomDomain + '/*'],
js: ['scripts/content-banners.js'],
runAt: "document_start"
js: ['/scripts/common-functions.js', '/scripts/content-banners.js', '/scripts/content-breezewiki.js'],
runAt: "document_idle"
}]);
chrome.storage.sync.set({ 'breezewikiCustomHost': breezewikiCustomDomain });
document.getElementById('breezewikiCustomHostStatus').innerText = 'Successfully added';