User blog comment:Rappy 4187/Technical Update: November 2, 2016/@comment-24473195-20161103171231/@comment-24473195-20161104111926

Reporting is a double-edged sword in this specific case because:

a) This was already reported twice on these technical updates, and presumably there is already a previous ticket as staff acknowledged it.

b) There is a very good description on Wikimedia's task management / issue tracker of a similar or perhaps identical problem.

c) Reporting to wikia is a bit like sending a nuclear bomb into a black hole. Nobody truly knows what will happen.

Due to the fact that the issue tracker is private (even for non-private issues) people may end up pointlessly re-writing a very good explanation of a previous issue, or may report some non-issue entirely due to their ignorance. As many perceived "software defects" are just caused by environmental problems such as user scripts, browser extensions, the browser itself,  bad network connections, a misconception that some features are "bugs", and so forth.

The only novelty of this report is the fact that searching for namespaces causes a pretty bad responce that could at the very least be handled in a similar or identical way as the previous "whitespace" issue.

Anyway, thanks for creating the ticket.