![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 102 minutes ago
#65635 new defect (bug)
provide an alternative to the XSLT stylesheet processing instruction for XML Sitemaps since browsers are phasing out support for it
| Reported by: | pbiron | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Sitemaps | Version: | 5.5 |
| Severity: | normal | Keywords: | 2nd-opinion |
| Cc: | Focuses: |
Description
This ticket is a follow-up to ticket:51117#comment:24.
In that comment @westonruter noted that Chrome (and other browsers) will soon deprecate and remove support for XSLT within the browser https://developer.chrome.com/docs/web-platform/deprecating-xslt Removing XSLT for a more secure browser on/about Nov 17, 2026 (which is after WP 7.1 but before WP 7.2).
When browsers do remove support for XSLT, then users who are used to loading /wp-sitemap.xml in their browser are likely to be confused because it will display the raw XML and not the currently rendered HTML sitemap.
Chrome and Firefox (I think) are considering releasing browser plugins that would provide XSLT support for anyone who has those browser plugins installed, but I think core should provide a more "natural" solution that doesn't require users install any such browser plugins.
I've been working on a patch that will allow users to load /wp-sitemap.html in the browser and get the current HTML rendering of their sitemap, by applying the existing XSLT styelsheet server-side. Of course, /wp-sitemap.xml will continue to provide the raw XML sitemap. At this point I'd say the patch is little more than a "proof-of-concept" and not yet ready to even post here.
Before continuing to work on that patch I wanted to start discussion of this issue and see if others think it is worth putting more time into.
