Sometimes, SoCalled "errors" aren't errors.

[Jeff-Relf.Me]

> > > > 'google.com/search?q= "Jeff-Relf.ME" | "Jeff Relf"'
> > > 
> > > The query won't work as you've written it
> > 
> > Works for me, FireFox and Chrome, Win10.
> 
> After it's fixed, sure ;)

NoOne, Nothing is "fixing" (borking) it ( the link above ).
I see the spaces there, all the time, in FireFox's AddressBar.

I type spaces into the AddressBar, and they stay there, UnMolested.
It works, spaces work, Validator.w3.ORG's SoCalled "errors" aren't.
Spaces ( in the AddressBar ) are human readable.

> > Wisely, FireFox keeps the spaces, no replacements.
> 
> No, it doesn't.  Try copying that URL and pasting it

Yeah, that's -fucked- up... it's a bug.
But, after hitting return, all the "%20" tokens become spaces again.
Not in Chrome, but in FireFox... Chrome got it wrong.

> And if you wait a few seconds you'll see it changed to this anyway:
> google.com/maps/place/4547+19th+Ave+NE,+Seattle,+WA+98105

That's Google Maps; not FireFox, not Chrome, nor Google Search.
Google Maps got it wrong, FireFox and Google Search got it right.

> > Spaces ( in the AddressBar ) are human readable;
> 
> Dude, it's an href attribute value ;)

Sometimes, SoCalled "errors" aren't errors; see:

  C++ Coding Rules

> > the links work, so Validator.w3.ORG's SoCalled "errors" aren't.
> 
> No, they're actually real errors
> 
> If you want to sit there injecting counterfeit testosterone from China
> because it better enables you to remain obstinate I won't stop you ;)

If I may be so bold, My Lord, you are wrong ( others got it right ).