Browser feature documentation is out of date with recent product changes

[gawainer36-lgtm]

Absolutely, Gavin. Here's a sharply worded draft you could send to Microsoft’s Edge documentation or product feedback channels. It’s professional, but direct—and it reflects your frustration with precision and clarity.

---

Subject: Urgent: Inconsistent and Outdated Edge Documentation Is Undermining User Trust

To the Microsoft Edge Product and Documentation Teams,

I’m writing to express deep frustration with the persistent disconnect between Microsoft Edge’s evolving UI and the documentation that’s supposed to support it. As a technically proficient user, I expect Microsoft—of all companies—to maintain accurate, up-to-date instructions for its own browser. Instead, I’m routinely met with outdated help articles, broken navigation paths, and third-party guides that reflect deprecated settings layouts.

Case in point: the JavaScript settings. Multiple sources—including enablejavascript.com and even some Microsoft support pages—still reference a “Site permissions” section that no longer exists in the current Edge build. This isn’t a minor oversight. It’s a systemic failure to align documentation with product changes, and it actively wastes users’ time while eroding trust in Microsoft’s ability to support its own tools.

If Microsoft is going to push frequent UI updates, then it must also commit to a rigorous documentation audit process. That means:

• Flagging and updating help articles with every major build
• Providing version-specific instructions for enterprise and consumer users
• Actively removing or redirecting outdated content from official channels

Doesn't anyone coding for Edge know about this?

Sincerely,
Gawaine Ross
Boston, MA
Power user, developer advocate, and someone who expects better

---

If you’d like, I can help you submit this through Microsoft’s feedback channels or tailor it for a public post on developer forums to get traction. Want to refine it further or add technical examples?

[kypflug]

Hi @gawainer36-lgtm , thanks for sharing the issue - I understand the frustration with out of date documentation, and I'll be following up internally with the product team to address your feedback. It would be helpful if you could clarify/confirm a few details to make sure I'm capture your concerns.

It sounds like you're primarily referring to browser feature documentation rather than developer documentation - e.g. the specific example of site permissions settings UI not matching the guidance in Microsoft support pages. Could you confirm that that's the case?

If possible, it would be very helpful if you can share any example links to Microsoft resources (docs, support pages, marketing pages, etc.) which are out of date, either for the site permissions settings mentioned above or for other examples.

Thanks again for the feedback and for any additional details you can provide!

[gawainer36-lgtm]

I couldn't see how to answer you on Git Hub, so here goes. I was trying to open a link to fortec.com. It opens fine in Firefox, but it paralyzed Edge. With Copilot we dug into possible reasons. It's not a site heavy with visuals or animations - it's very simple. Copilot kept referring me to links that were outdated. Copilot didn't know what version of Edge I am using the very latest - but it kept referring me to outdated settings in older versions of Edge. Copilot suggested command lines in command prompt and in powershell. I didn't have powershell, so I went to the Microsoft store which has an outdated version (as so much of the software there is). So I went onto Github and there were several versions but not the version I needed, I think it was powershell 5.3. That wouldn't download and install (Windows 11, most recent update 10/17/25). Copilot couldn't solve the problem. Thanks, Gawaine Ross

…

On Fri, Oct 17, 2025 at 3:37 PM Kyle Pflug ***@***.***> wrote: *kypflug* left a comment (MicrosoftDocs/edge-developer#3610) <#3610 (comment)> Hi @gawainer36-lgtm <https://github.com/gawainer36-lgtm> , thanks for sharing the issue - I understand the frustration with out of date documentation, and I'll be following up internally with the product team to address your feedback. It would be helpful if you could clarify/confirm a few details to make sure I'm capture your concerns. It sounds like you're primarily referring to browser feature documentation rather than developer documentation - e.g. the specific example of site permissions settings UI not matching the guidance in Microsoft support pages. Could you confirm that that's the case? If possible, it would be very helpful if you can share any example links to Microsoft resources (docs, support pages, marketing pages, etc.) which are out of date, either for the site permissions settings mentioned above or for other examples. Thanks again for the feedback and for any additional details you can provide! — Reply to this email directly, view it on GitHub <#3610 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BWOGCO7EPCH7YOSVC5KMLZL3YFAQTAVCNFSM6AAAAACJO3G44OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJWGU2DCMZTGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[captainbrosset]

@gawainer36-lgtm you initially mentioned "systemic failure to align documentation with product changes", but you're now refering to Copilot's inability to link you to up to date resources. I believe these are different things.
Whether Copilot has the right training and real-time data to point you to the right resources is a different issue than whether those resources exist at all.

Thank you for the initial feedback about outdated docs, which Kyle has sent to our internal teams, to make sure they're aware.
It would be very helpful if you could reply to the questions in Kyle's message above too.