Was this, in theory, fixed? It’s still not consistent.
What I see now is that #Foo and #foo combine in the tags pane as #foo. However, the search is still case-sensitive, so clicking on that only shows pages with #foo lowercase.
Similarly, searching tag:#Foo finds one and tag:#foo finds the other (which makes sense they’d have the same behavior as the pane, since the tag pane is just driving the search pane).
One thing that’s interesting, if only “#Foo” exists, the tag pane shows it in uppercase. If both “#Foo” and “#foo” exist, it only shows lowercase. No idea what inner mixed case would do, but point is that it defaults to a behavior that excludes the case it’s hiding.
Either they should stay separate in the tags pane, or (preferably to me) tags just become case-insensitive in searches as well.
I realize I could do an ignore-case: at the front of every tag:, but that’s pretty onerous. There’s already an issue with saved regex searches being nigh unreadable because there aren’t labels and can’t easily be seen in their entirety. Having to add an ignore specifier would make them even longer (though I might suggest ic: as an abbreviation, seeing how most other query languages just use that or i).