The colour filter function is broken due to asset versioning in the build process for the CSS in the sa11y library.
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:
| Labels |
Added:
No Code Attached Yet
|
||
| Labels |
Added:
bug
|
||
@LadySolveig you will be more familiar than me as you;ve previously worked on this versioning but shouldnt this be vendor not vendors
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.
@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.
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?
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-12-23 10:34:06 |
| Closed_By | ⇒ | LadySolveig |
i am NOT convinced that changing the folder name is correct so i wont change it as i dont understand it
@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
vendorfolder 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.
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