S3fsCssOptimizer rewrites CSS that is stored locally when use_s3_for_public is on

Observe they are rewritten by the module

I recalled looking at this when we added support for assets:// and thinking “why don’t I need to disable this? Links are generating correctly but why?” and convinced myself that it was something with how the file pas passed over and location bypasses changing it to s3fs, I completely missed the script converting relative to absolute.

Do not override asset.css.optimizer if > drupal 10.1?

That would be the best solution.
Simple \Drupal::version < 10.1 comparison before overriding is likely sufficient.

Opened MR with the change from above - it doesn't look like this would be applicable to v4 as the css / js functionality is in a sub module which could just be disabled (I assume - have not tested or looked at the 4.x branch)

4.x should be fine as it is a submodule and can be enabled/disabled by choice (and there is a good chance I’m going to remove the code completely once D11 comes out).

Small change by maintainer prior to merging (caused by maintainer direction lacking sufficient detail in initial review).

Thanks for locating this issue. Merging to Dev. Should go out this week when we tag D11 support.

Automatically closed - issue fixed for 2 weeks with no activity.