Views contextual filters with multiple values do not work with arguments containing spaces

There is a bigger problem here, which imo is relevant to this thread.

Because of how this regex is written - [\w0-9-_\.], contextual filters do not work with arguments that contain any non-word characters.

Just about any special character including common ASCII - !@#$%^&*()/\<>?"'~`= for example - will break the regex, and the view will silently fail.

IMO, a proper fix would address this failure, and not be limited to this one very specific shortcoming about whitespace.

Also needs tests to prevent further regression.

Here are tests that will demonstrate the failure with regard to special characters and spaces.
While writing these tests, I discovered that existing tests already account for the undocumented space-delimiting behavior of the contextual argument handler, dating back to views 7.x, before it was included into core.

So, bug or not, any change may break contrib space and will require a change record.

Will need framework maintainer to weigh in as well.

The last submitted patch, 27: 3034595-27-TEST-ONLY.patch, failed testing. View results →

I've spent the last few hours troubleshooting an issue that came down to exactly what AaronBauman mentions in #26. In my case, the field has an equals sign (=). I may be able to come up with a workaround for my case, but a fix for this would be greatly appreciated.

The patch #24 failed when using an argument without any spaces and contextual filter options "Allow multiple values" and "Preserve spaces with multiple values" enabled. So I re-rolled patch against #24 in Drupal 10.2.x.

The last patch does not provide tests.

Since patches are no longer tested, a merge request needs to be provided.

I updated the last patch so now it includes tests. It was applied on Drupal 10.x