[Bug]: Edge 150.0.4078.65+ regression - printerProvider listeners never dispatched #741

Activity

1. Rahul-Bauri

   self-assigned this

   on Sep 1, 2026
2. Rahul-Bauri

   added

   Bugthe issue is a code defect that should be fixedthe issue is a code defect that should be fixed

   Trackedthe issue is valid and tracked on our backlog.the issue is valid and tracked on our backlog.

   Edge AddonsLabel to filter all items related to Edge AddonsLabel to filter all items related to Edge Addons

   on Sep 1, 2026
3. Rahul-Bauri

   added the

   Bug

   issue type on Sep 1, 2026
4. Rahul-Bauri commented on Sep 1, 2026

   

   Rahul-Bauri

   on Sep 1, 2026

   Collaborator

   More actions

   Hi Mike (@peevees)

   Could you please provide a downloadable sample ZIP package that reproduces the issue? The GitHub package referenced above does not appear to work on our side, so we are unable to reproduce the problem using it.

   

   Additionally, if possible, please share relevant screenshots that demonstrate the issue. These will help us better understand and investigate the problem. Thank you.
5. Mike (peevees)

   added a commit that references this issue on Sep 2, 2026

   Restructure as mv3/mv2 builds with full printerProvider tracing

   ...

   c1f794b
6. peevees commented on Sep 2, 2026

   

   Mike (peevees)

   on Sep 2, 2026

   Last edited by peevees

   Author

   More actions

   Hi Rahul-Bauri - I've updated the test extension to make this easier to observe, and attached it as ZIP: printerTestBare-mv3.zip. Source: https://github.com/peevees/printerTestBare

   It now traces every stage of the handshake, so you can see exactly where the chain stops.

   Repro

   1. Unzip and load the mv3 folder via edge://extensions → Developer mode → Load unpacked.
   2. On the extension's card, click Inspect views: service worker to open the background console. (Inactive there is normal — clicking it starts the worker.)
   3. Open any page and press Ctrl+P. Not Ctrl+Shift+P, which opens the Windows system dialog.
   4. Open the printer dropdown and look for "Testprinter".
   5. In the background console, look for onGetPrintersRequested FIRED. If the console was closed in between, run dumpTrace() — the trace is mirrored to chrome.storage.local, so it survives a worker teardown.

   What we observe

   In Edge, registration succeeds:

   [ptest] api.available {onGetPrintersRequested: 'object', onGetCapabilityRequested: 'object', onPrintRequested: 'object', onGetUsbPrinterInfoRequested: 'object'}
   [ptest] register.done {event: 'onGetPrintersRequested',   hasListener: true}
   [ptest] register.done {event: 'onGetCapabilityRequested', hasListener: true}
   [ptest] register.done {event: 'onPrintRequested',         hasListener: true}
   [ptest] permissions.printerProvider {granted: true}
   

   Opening print preview then appends nothing — no FIRED line, no error, no warning. Testprinter is absent from the dropdown, which lists only local and PDF destinations.

   The same folder, unchanged, in Chrome 152 on the same machine:

   [ptest] onGetPrintersRequested FIRED
   [ptest] onGetPrintersRequested resolved [{…}]
   [ptest] onGetCapabilityRequested FIRED {printerId: 'printer'}
   [ptest] onGetCapabilityRequested resolved
   

   and Testprinter appears in the destination list. Running the same ZIP in both browsers is the quickest way to see the difference. Screenshots of both consoles and both destination lists are attached.
7. peevees commented on Sep 7, 2026

   

   Mike (peevees)

   on Sep 7, 2026

   Author

   More actions

   Rahul-Bauri any news? any information missing that is needed?
8. TheRealJohanJ commented on Sep 21, 2026

   

   TheRealJohanJ

   on Sep 21, 2026

   More actions

   Rahul-Bauri is there any progress on this issue?