Open
Bug 1899538
Opened 9 months ago
Updated 8 months ago
The "SET_DEFAULT_PDF_HANDLER" action is not supported by the featureCallout template
Categories
(Firefox :: Messaging System, defect, P3)
Tracking
()
NEW
People
(Reporter: cfat, Unassigned)
References
(Blocks 1 open bug)
Details
[Affected versions]:
- Firefox Release 126.0.1 (Build ID: 20240526221752)
- Firefox Beta 127.0b7 (Build ID: 20240527091822)
- Firefox Nightly 128.0a1 (Build ID: 20240529013712)
[Affected Platforms]:
- Windows 10
[Prerequisites]:
- Have Firefox installed.
- Have a non-Firefox app set as default for .pdf files. (e.g. Adobe Acrobat)
- Have following pref set:
browser.newtabpage.activity-stream.asrouter.devtoolsEnabled
= true
[Steps to reproduce]:
- Open the browser using the profile from the prerequisites.
- Navigate to about:asrouter.
- Delete the content of any message and paste the JSON config for "SET_DEFAULT_PDF_HANDLER" featureCallout from here.
- Click the "Modify" button.
- Click the "Primary button" of the message.
- Open the Default apps OS window and observe the default app for .pdf files.
[Expected result]:
- Firefox is set as the default app for .pdf files.
[Actual result]:
- Firefox is NOT set as the default app for .pdf files.
[Notes]:
- This is reproducible when using featureCallout and infobar messages with the "SET_DEFAULT_PDF_HANDLER" action.
- The following error is displayed in the Browser Console after clicking the primary button:
Error: WDBA nonzero exit code 2147500037: ErrExeOther
Updated•9 months ago
|
Summary: Firefox is not set as the default pdf handler via messages "SET_DEFAULT_PDF_HANDLER" action → The "SET_DEFAULT_PDF_HANDLER" action is not supported by the featureCallout template
Comment 1•8 months ago
|
||
Not currently blocking any experiments but this is an action we want to support.
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•