My typical workflow is to search for something like this (tags change over time):
[c++20] or [c++23] or [c++26]
This worked up until today. Now, while a single tag search works fine, the multi-tag search with ors turns into [c][20] or [c][23] or [c][26], which then fails to find anything at all because [20], [23], and [26] aren't valid tags.
+in the URL. However, apparently after the fix the+which is part of the tag is now broken. The character is escaped correctly to%2bbut apparently ignored.[c++*]still works, despite expanding to a query you cannot run directly (due to length and this bug)./questions/tagged/c%2b%2b*and seems to be interpreted fine. Searching[c++20]also works. It seems it's when there is more than one tag that the issue triggers.[c++] -[c++20]and you get a search for[c+++-c++20]. But swap the positions and which one is negated, then[c++20] -[c++]leads you to[c] [20] -[c][c#*]ends up searching for only[c#]C#under the "Popular tags" of the community activity widget. It does not happen when I click aC#badge under a postc%2b%2b20+or+c%2b%2b23gets parsed asc+++or+c++23, which makes it equivalent toc or c 23, whoops.+when I made the fix in Doing a tag search and changing the sorting via the navigation buttons breaks queries with operators. The intended encoding was to encode spaces as%20instead. I've got a fixed developed and will get it built out for y'all as soon as it gets reviewed and approved.