Bug: Fragment identifier in commandline args is escaped

I sent this to chromium-discuss mailing list, but it's still awaiting 
approval. I'm sending this again in hopes that someone might know a 
workaround for this.

Running:

$ chromium '/path/to/out.html#header'

Results in chromium opening file:///path/to/out.html%23header

Expected opening the original file and selecting the desired fragment 
identifier.

It would be better to leave the escape to the user invoking the chromium 
command, and fallback to internal escaping in case that didn't work.

Avid