Different results with &source=chrome.ob

oneiricsky

With the addition of the &source=chrome.ob parameter, the results pages presents different results and shows a filter as applied when there is none.

With &source=chrome.ob

Without &source=chrome.ob

&source=chrome.ob shouldn't act as a filter and should give the same results as without the source parameter.

nobodywasishere

Where did you hear about this parameter?

oneiricsky

nobodywasishere I noticed it today while searching through Edge's address bar

edit: grammar

z64

Despite the UI change this doesn't do anything to the search that is performed, it is just some wires crossed with the Videos filter UI code. The different results are incidental; the upstream sources we use are not deterministic in the results they give us.

oneiricsky

z64

Thanks for the clarification. In that case, would it be appropriate to update this report to just being a UI bug?