No Code Attached Yet bug
avatar LadySolveig
LadySolveig
23 Dec 2025

The colour filter function is broken due to asset versioning in the build process for the CSS in the sa11y library.

Image

The actual problem in our implementation is that it cannot find the resource for the SVG – for the actual filter.
For example:

[data-sa11y-filter="tritanopia"] :not(sa11y-control-panel, sa11y-dismiss-tooltip) {
  filter: url(#sa11y-tritanopia?v=176643);
}

If I remove the version appendix like this

filter: url(#sa11y-tritanopia);

ref: #46600 (comment)

Affected versions:

  • Joomla 5.4
  • Joomla 6.0
  • Joomla 6.1
avatar LadySolveig LadySolveig - open - 23 Dec 2025
avatar joomla-cms-bot joomla-cms-bot - change - 23 Dec 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 23 Dec 2025
avatar Fedik Fedik - change - 23 Dec 2025
Labels Added: bug
avatar Fedik Fedik - labeled - 23 Dec 2025
avatar LadySolveig LadySolveig - change - 23 Dec 2025
The description was changed
avatar LadySolveig LadySolveig - edited - 23 Dec 2025
avatar brianteeman
brianteeman - comment - 23 Dec 2025

I can confirm that removing the asset versioning fixes the problem.

changing the width to 100vw was not required to fix the problem and should be reported upstream

avatar brianteeman
brianteeman - comment - 23 Dec 2025

@LadySolveig you will be more familiar than me as you;ve previously worked on this versioning but shouldnt this be vendor not vendors

avatar LadySolveig LadySolveig - change - 23 Dec 2025
The description was changed
avatar LadySolveig LadySolveig - edited - 23 Dec 2025
avatar LadySolveig
LadySolveig - comment - 23 Dec 2025

You're right, the width setting has nothing to do with the fix or the function at all. I was completely on the wrong track there.
I don't think it's a bug at all. Sorry for this confusion.

avatar LadySolveig
LadySolveig - comment - 23 Dec 2025

@LadySolveig you will be more familiar than me as you;ve previously worked on this versioning but shouldnt this be vendor not vendors

joomla-cms/build/build-modules-js/versioning.mjs

Line 17 in 2ccd259
'vendors',

I would say your assumption is correct, as there is only a vendor folder in the `build/media_source folder after execution of npm ci / i.

However, since sa11y is not part of this folder, this is unfortunately probably an additional bug and unrelated to this one.

avatar LadySolveig
LadySolveig - comment - 23 Dec 2025

Line 17 in 2ccd259
'vendors',

Could you please create a PR on 6.1-dev for this find @brianteeman so that it can be tested more extensively before it goes into production?

avatar LadySolveig LadySolveig - change - 23 Dec 2025
Status New Closed
Closed_Date 0000-00-00 00:00:00 2025-12-23 10:34:06
Closed_By LadySolveig
avatar LadySolveig LadySolveig - close - 23 Dec 2025
avatar LadySolveig
LadySolveig - comment - 23 Dec 2025

Since there is a fix, I am closing this issue. We would greatly appreciate your help in testing it! #46609

avatar brianteeman
brianteeman - comment - 23 Dec 2025

i am NOT convinced that changing the folder name is correct so i wont change it as i dont understand it

avatar LadySolveig
LadySolveig - comment - 23 Dec 2025

@LadySolveig you will be more familiar than me as you;ve previously worked on this versioning but shouldnt this be vendor not vendors
joomla-cms/build/build-modules-js/versioning.mjs
Line 17 in 2ccd259
'vendors',

I would say your assumption is correct, as there is only a vendor folder in the `build/media_source folder after execution of npm ci / i.

However, since sa11y is not part of this folder, this is unfortunately probably an additional bug and unrelated to this one.

@dgrammatiko could you have a look into this one and and possibly create a PR for 6.1. Seems to me like a valid find.

Add a Comment

Login with GitHub to post a comment