Thanks for reporting this issue with a detailed write-up.

Unfortunately, this is an implementation choice made by google.com, and is not a Chrome bug so I am marking it as WontFix.

You simply can't ignore this bug as it is not maintaining the consistency of search operation .
I have already attached the detailed steps to replicate the issue.

Also other browsers are not showing such kind of anamoly, there screenshots are also added in previous attachment with Chrome's nOt sO cOnSiStEnT bEhAvIoUr(consistent behaviour!!!!)

Even if this is an implementation choice made by GOOGLE, but its a major security concern!!


Google is running such a huge program "BUG BOUNTY" aiming to find security issues.
The points which were not considered during initial designing OR irrational behaviour of logic are CALLED AS BUG!

Yes I acknowledge the decision of Google team but this can be easily exploited and made a huge security concern!

You are closing this incident as WontFix stating that it's a Google implementation (open point left while designing)than there is no point of finding bug and alerting Google. 

I am expecting that proper communication within team must be taken place before any exploitation of these inconsistent behaviour. Which is not observed in other competitors Browsers viz MOZILLA FIREFOX as per screenshots in previous attachment.

Regards,
Karam Singh

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot