It's technically correct that www.example.com and example.com are different domains and can serve different stuff.

So are https://example.com and http://example.com.

If you serve materially different content based on small differences, that's user-hostile, and common tools have no obligation to support you. Chrome shouldn't cater to sites that change behavior based on a www prefix, because the vast majority of users expect those sites to be the same. Hiding the prefix won't change their mind.