Steps to reproduce the problem:
Browse a content:// URL and then attempt to browse it again later, after you forgot its exact path.

What is the expected behavior?

What went wrong?
It would be very productive if content:// URLs were saved in the
browser's history, just like file:/// URLs are on the desktop.

The user was happily browsing e.g.,
content://com.asus.filemanager.OpenFileProvider/file/sdcard/zzz/weatherURLs.txt
and now he wants to browse it again, but e.g., can't even remember how
he got there, --- which all could be avoided if content:// URLs were
saved in History. In fact it is a bug that they are not.

I'm not asking that they be shared with the users other devices'
history, just that they be given the same fair treatment that file:///
URLS have on Desktop.

Did this work before? No 

Chrome version: 72.0.3579.0  Channel: canary
OS Version: 
Flash Version: