librewolf/issues
25
145

Please keep XSLT #2978

Closed
opened 2026年04月16日 15:49:12 +02:00 by mro · 2 comments

Operating System

All / Agnostic

Feature Description

Mozilla follows google in decomissioning xslt.

Please keep this feature to keep documents readable that require it.

Problem / Use Case

XSLT has been a w3c standard since 1999 and many documents rely on this mechanism to separate content from markup, not just css. Google dislikes that https://www.jwz.org/blog/2025/08/xslt/ and mozilla follows the money. Today the librewolf console said to me " XSLT will be removed from this web browser soon. See https://github.com/mozilla/standards-positions/issues/1287".

I urge you to please keep this important feature to separate (possibly immutable) content from markup and css and render it without code on the server, in.

### Operating System All / Agnostic ### Feature Description Mozilla follows google in decomissioning xslt. Please keep this feature to keep documents readable that require it. ### Problem / Use Case XSLT has been a w3c standard since 1999 and many documents rely on this mechanism to separate content from markup, not just css. Google dislikes that https://www.jwz.org/blog/2025/08/xslt/ and mozilla follows the money. Today the librewolf console said to me " XSLT will be removed from this web browser soon. See https://github.com/mozilla/standards-positions/issues/1287". I urge you to please keep this important feature to separate (possibly immutable) content from markup and css and render it without code on the server, in.

I don't think it makes a lot of sense for LibreWolf to keep maintaining XSLT support independently from Firefox if they deprecate it.

LibreWolf focuses on security and privacy, not really on supporting old web standards.
This would add additional security concerns, and also fingerprinting aspects.

Also I want to make clear, this is not a question of "just not deleting it". Keeping something like this would mean actively maintaining it, adopting it to all coming changes and updates to the XML library and would basically mean completely rewriting it should Mozilla really decide to replace libexpat eventually. This is just completely unreasonable considering the minimal use XSLT has nowadays.

I don't think it makes a lot of sense for LibreWolf to keep maintaining XSLT support independently from Firefox if they deprecate it. LibreWolf focuses on security and privacy, not really on supporting old web standards. This would add additional security concerns, and also fingerprinting aspects. Also I want to make clear, this is not a question of "just not deleting it". Keeping something like this would mean actively maintaining it, adopting it to all coming changes and updates to the XML library and would basically mean completely rewriting it should Mozilla really decide to replace libexpat eventually. This is just completely unreasonable considering the minimal use XSLT has nowadays.
Author
Copy link

the manstream often has difficulties acknowledging the urge of minorities. We see such in many fields, especially when argued for diversity the quantity-argument is a slippery slope. Ultimately that can lead to a fascism of the majority.

I understand that librewolf doesn't want to maintain an engine, but you were my first stop as librewolf, being niche itself, may understand the diversity argument better than bigger organsations. Especially when those are funded by the bullies that put the axe on the root of this foundational internet standard.

There's a big amount of documents out there - many published raw xml data, rdf, feeds - that will cease to render for humans. If tools like browsers don't care about backward compatibility concerning w3c standards that are in for decades, we're in a dire situation.

Anyway, thanks for looking into it and bearing with me.

the manstream often has difficulties acknowledging the urge of minorities. We see such in many fields, especially when argued for diversity the quantity-argument is a slippery slope. Ultimately that can lead to a fascism of the majority. I understand that librewolf doesn't want to maintain an engine, but you were my first stop as librewolf, being niche itself, may understand the diversity argument better than bigger organsations. Especially when those are funded by the bullies that put the axe on the root of this foundational internet standard. There's a big amount of documents out there - many published raw xml data, rdf, feeds - that will cease to render for humans. If tools like browsers don't care about backward compatibility concerning w3c standards that are in for decades, we're in a dire situation. Anyway, thanks for looking into it and bearing with me.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
Branding
Issues that relate to our logo or the branding of our browser and website.
Broken Upstream
Issue is also present in Firefox
Build
Alpine
Issues specific to the Alpine Linux build of LibreWolf.
Build
AppImage
Issues specific to the AppImage release of LibreWolf.
Build
AUR
Issues specific to the AUR build of LibreWolf.
Build
Debian
Issues specific to our official release for Debian based distros.
Build
DebianOBS
Issues specific to the non-official OBS build of LibreWolf.
Build
Fedora
Issues specific to our official release for Fedora.
Build
FedoraCOPR
Issues specific to the non-official COPR build of LibreWolf.
Build
Flatpak
Issues specific to the Flatpak release of LibreWolf.
Build
Gentoo
Issues specific to the Gentoo build of LibreWolf.
Component: Infrastructure
Issues related to infrastructure provided by LibreWolf
Component
Builds
Issues related to how we build LibreWolf
Component
Patches
Issue with one of the patches in our source code.
Component
Settings
Issues related to the settings of LibreWolf.
Component
UI
A purely cosmetic issue in our browser.
Component
Website
Issues with our website.
Docs
Change required
A needed change in our documentation.
Docs
FYI
Issues that document a change, or how stuff gets patched, built or configured.
Flag
Caution
Change that might be tricky or that needs to be carefully evaluated. Best suited for core members.
Flag
Good first issue
Suited for a first contribution as it is a straightfoward task!
FreeBSD
Issues related to the FreeBSD release of LibreWolf.
Linux
Issues realted to one or all our Linux releases.
macOS
Issues realated to the MacOS release of LibreWolf.
Needed
Help
We are stuck :-(
Needed
Info
Closing in ten days if no details are provided.
Needed
Testing
We are almost there!
Prio
High
Issues with a high priority
Prio
Low
Prio
Normal
Prio/Urgent
Issues needing immediate attention
Repositories
An issue with our repositories.
Research
Collecting informations to document something or to evaluate a change.
Source
Issues related to the source code of LibreWolf.
Status
Blocked
An issue blocked by another one.
Status
Duplicate
Look for existing issues.
Status
Icebox
Change that is not happening soon or issue that cannot be tested.
Status
Known issue
An issue that we are aware of but that we cannot fix at the moment.
Status
Not Planned
The requested feature is currently not planned
Status
Upstream
Either we upstreamed the issue or a fix is coming directly from Mozilla!
Status
Won't fix
Does not require a fix.
Type
?
What?
Type
Bug
Ouch...
Type
Discussion
Let's have a talk...
Type
Feature
A feature request.
Type
Question
Not a issue but just a user question
Type
Task
This needs to be done
Windows
Issues related to the Windows release of Librewolf.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
librewolf/issues#2978
Reference in a new issue
librewolf/issues
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?