undefined | Better HN

0 pointstaeric5y ago0 comments

Feels like it to me. I'd expect the zoom to be associated with the site.

Granted, I am probably importing old thoughts of it being a sort of user provided style sheet.

0 comments

It'd make the zoom level you see jump up and down depending on whether you lose your connection or regain it, this is less jarring.

You could say that Chrome is designed to tie the zoom level to the viewport but I wouldn't count on this behavior springing up from an underlying design and implementation rather than it being a design choice for the user experience.

taericOP5y ago

I'm not sure I follow. If the page is constantly bouncing to the no connection page, it is jarring, period. If the page of my "no connection" changes because of the address in trying, that is jarring if the problem is on my end.

That is, consider your network is down. You try to go to an address. It doesn't load, so you try another address, the page changes; but it is the same content.

forgetfulness5y ago

Is it important that the no connection message be an HTML document treated like others in the web browser? If browsers used to model it that way and you saw behaviors corresponding to the switching of a webpage, it was arbitrary too, and in this case, would cause more disruption.

hn_throwaway_995y ago

> I'd expect the zoom to be associated with the site.

That's what the GP comment said happened: the zoom level was the one associated with what they previously had set on HN, and they expected it to be the opposite, the default zoom level for the browser.

taericOP5y ago

But the site didn't load. My browser's not loading page did.

Is easier to see as broken by thinking of "how could I set it so that my browser's error page has a default zoom?"

derefr5y ago

But your browser's connection-failure page is considered to come from the HTTP Origin of the site. It's like when browsers receive a specific HTTP status-code (e.g. 500) with no body, so they render a default HTML error document.

In both cases, those are the browser supplying a resource representation, while still technically being on the resource specified in the navigation bar. The thing you're seeing is an overridden representation of the server's response. (Which, in this case, just happened to be "no response.")

It's almost exactly the same as how the server sending a 304 gets the browser to load the document from cache. The server's actual response was a 304; but the browser's representation of that response is the cached HTML DOM it had laying around from the last 2xx resource-representation it received "about" the same resource.

1 more reply

ncallaway5y ago

I would consider the browser's built-in page for "I couldn't load news.ycombinator.com" to be a separate site from "news.ycombinator.com".

j / k navigate · click thread line to collapse

0 comments

forgetfulness5y ago

It'd make the zoom level you see jump up and down depending on whether you lose your connection or regain it, this is less jarring.

taericOP5y ago

That is, consider your network is down. You try to go to an address. It doesn't load, so you try another address, the page changes; but it is the same content.

forgetfulness5y ago

hn_throwaway_995y ago

> I'd expect the zoom to be associated with the site.

taericOP5y ago

But the site didn't load. My browser's not loading page did.

Is easier to see as broken by thinking of "how could I set it so that my browser's error page has a default zoom?"

derefr5y ago

1 more reply

ncallaway5y ago

I would consider the browser's built-in page for "I couldn't load news.ycombinator.com" to be a separate site from "news.ycombinator.com".

j / k navigate · click thread line to collapse