No we don't want to change the whole browser's default magnification. We just want localhost to be treated fairly like any other site, as far as remembering zoom levels are concerned.

Unable to reproduce this issue on Ubuntu 14.04 using chrome latest stable #62.0.3202.94 by following steps mentioned below.

1. Saved a sample html file in Desktop
2. Started python -m SimpleHTTPServer in terminal
3. Navigated to http://localhost:8000/
4. Opened the saved html file, zoomed in and closed the web page
5. Opened the same local host file, observed the page remembers the zoom percent as expected.

jidanni@ Could you please confirm the above steps is the right way to reproduce this issue? If not, please provide the test steps along with a test case to check this issue from Chrome testing team.

Thanks!

Test 1: for a single file:///, is zoom remembered across sessions?
$ chromium file://$PWD/x.pdf
Hit CTRL+++++
Hit CTRL+W
$ chromium file://$PWD/x.pdf
We see zoom was not remembered for PDFs.
(Repeating the experiment with HTML shows that zoom IS thankfully remembered for
.html files.)

Test 2: is zoom carried on for the entire "site"?
$ chromium file://$PWD/x.html
Hit CTRL+++++
$ chromium file://$PWD/y.html
Here we see that x's current zoom is not extended to y.
Y is still at default zoom.

I.E., if one zooms one page of fb.com, all other pages there get the
same zoom.

However if I zoom one file:/// URL no other file:/// URLs are tandemly
zoomed. Even if all live in the same directory.

$ cd /usr/share/doc/openjdk-8-jre-headless/jre/api/plugin/dom/index-files/
$ ls
index-1.html   index-12.html  index-15.html  index-18.html  index-20.html  index-5.html  index-8.html
index-10.html  index-13.html  index-16.html  index-19.html  index-3.html   index-6.html  index-9.html
index-11.html  index-14.html  index-17.html  index-2.html   index-4.html   index-7.html
$ chromium *
Hmmm, seems a little small, so the user uses CTRL+++
But then must do the same for EACH file. (Or mess up his global Settings, just
for this directory.)
That is because chromium doesn't consider the local machine as just
another website... it should!

Note all along I am not talking about any HTTP server transactions at
all. I am just talking about reading from the local disk. So yes, me
saying 'localhost' was confusing. (I didn't test if http://localhost/
worked like http://example.com/ . I hope it does.)

Also by file:/// files, I mean local files, with or without the file: +
slashes prefix scheme.

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Yes, after all the above file:/// cases, you can check if the same paths, but served over your localhost:8000 server also are working. Glad to hear at least in your step 5 that case is.

Could you please update the thread,if you still facing this issue on the latest stable 66.0.3359.181/Canary 68.0.3436.0.

can we close this issue?, please let us know for further action.

Thanks,

*** UI Mass Triage ***

Closing, since there is no updates since the past few weeks.
If you feel this issue should still be addressed, feel free to reopen it or to file a new issue.