How can I pin a local HTML file opened in Edge to the taskbar?

Question

I wrote a simple html file and saved it to my local drive. I can open this file in Edge just fine, but Edge won't let me pin it to the Windows taskbar.

So, I created a new shortcut on the desktop using the target

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" -inprivate -new-window file:///C:/Users/user/path/file.htm

This shortcut launches a new in-private Edge window with the html file just fine. I also can pin that shortcut to the taskbar. However, when it launches, Windows puts it under the Edge icon, and not the shortcut icon. So, successive clicks of the shortcut taskbar icon just launches new Edge windows, even if the shortcut is already open.

How do I get this taskbar icon to show it open as that icon, and not as another normal Edge window under the Edge icon (and so only one can be open at-a-time)? Additionally, it would be nice to have it open without the tab bar or controls like navigation buttons or favourites menus. I want it to launch my html file in an Edge in-private window with no controls on it (aside from the Windows minimize/maximize/close controls).

Answer 1

Hi, thanks for reaching out to the Community. Let me find someone who can address your question.

Answer 2

Hi,

Thank you for writing to Microsoft Community Forums.

Seems that you want to pin the html file you created to taskbar and the option is greyed out. unfortunately, such feature is yet to be introduced in Edge chromium browser.

However, for a better clarity on your concern, I would suggest you to post your query in TechCommunityforums, where we have experts and support professionals who are well equipped with the knowledge on Edge feature to assist you with the appropriate troubleshooting steps.

Regards,

Aditya Roy

Microsoft Community – Moderator

Answer 3

Hi, Aditya.

I will post this question in the Tech Community, as you suggested, however I need to make one note here. The statement, "...such feature is yet to be introduced..." is not accurate. The feature is already in Edge, and available for use when using http or https. The fact that this feature does not work with the "file://" protocol means the Edge developers explicitly disabled the feature for this use case.

There is no reasoning, no explanation, no articles, nothing on why this design choice was made. Microsoft's policy is to tell customers to "just shut up and deal with it." If a design choice is made, I want to know why. If a bug in the software hasn't been fixed years after it was reported, I want to know why. If a feature is changed in an update, I want to know why.

I'm never told why...ever.

Answer 4

There's a fairly detailed run-down of the file:/ protocol in this text/plain article: Restrictions on File Urls. I didn't spot any reference to your specific problem, but you might be able to track down the reason for it in there somewhere.

When you post at TechCommunity, try tagging the article's author (a Senior PM on the Edge team). He's usually very accommodating: ericlaw (microsoft.com)