#1685 Fix side panel sample tab path setup

[Anonymous]

Originally created by: KirtiRamchandani

Summary

• Configure the tab-specific side panel path before the extension page button can open the panel.
• Have the content script request tab-specific setup before enabling its injected button.
• Keep the click-triggered path focused on chrome.sidePanel.open() so the first click opens sidepanel-tab.html.

Fixes [#1477].

Testing

• npx eslint functional-samples/cookbook.sidepanel-open/content-script.js functional-samples/cookbook.sidepanel-open/script.js functional-samples/cookbook.sidepanel-open/service-worker.js

[Anonymous]

Originally posted by: KirtiRamchandani

Closing this earlier version in favor of [#1695], which uses the preconfiguration approach for [#1477] so the click handler only needs to call chrome.sidePanel.open().

[Anonymous]

Ticket changed by: KirtiRamchandani

• status: open --> closed