Re:Ask HN: Why does Google put the query in the URL hash ins...
by michaelvillar on Monday January 09, 2017 @03:07AM
(#13354788)
They could use `pushState` to change the query without reloading the page?
[ Parent
| on HN ]
Re:Ask HN: Why does Google put the query in the URL hash ins...
by wmil on Monday January 09, 2017 @03:31AM
(#13354875)
They could if they were building it now. IE got pushState support in IE 10 in 2012.
The hash state has been there since Instant Search was launched in 2010.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by lloeki on Monday January 09, 2017 @08:39AM
(#13356196)
Graceful degradation/progressive enhancement is a thing, though.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by bpicolo on Monday January 09, 2017 @08:56AM
(#13356288)
The amount of money Google makes supporting older browsers is most likely measured in billions.
Not to mention, why fix something that isn't broken? There are cases for it, but it's roughly the same tech that it was 4 years ago. What would they gain by spending developer time on it?
Re:Ask HN: Why does Google put the query in the URL hash ins...
by iurisilvio on Monday January 09, 2017 @12:13PM
(#13357852)
Perfect. They definitely don't need optimization for search engines, which is probably the most important reason to a clean URL.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by adamdonahue on Monday January 09, 2017 @09:39AM
(#13356578)
Exactly. You are someone who gets it.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by heisenbit on Monday January 09, 2017 @02:14PM
(#13358904)
I suspect they spend a ton of developer time. It is their #1 source of income. What they won't do is releasing it unless it is 99.9% certain that it yields an improvement.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by untog on Monday January 09, 2017 @09:22AM
(#13356440)
Yes, but in this case the benefits of the enhancement are small enough that Google may have decided that consistent behaviour was more desirable.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by paulddraper on Tuesday January 10, 2017 @02:45AM
(#13363363)
Consistent and long-lasting support is a thing too.
Rare on today's web, but still a thing.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by thomasahle on Monday January 09, 2017 @05:52AM
(#13355415)
Would that not remove the possibility for sharing or manually editing the URL? (I'm asking because I don't know how much cool stuff pushState can do.)
Re:Ask HN: Why does Google put the query in the URL hash ins...
by dpark on Monday January 09, 2017 @09:58AM
(#13356724)
No, but it makes shared links less inefficient. If you share a URL like this, the server will not receive the hash on the initial request, so the js client will have to do the search as a second request after the page load. The reality is that most users will never even notice because it's still fast.
Manually editing the link causes that same fetch-render-refetch flow.
Edit: Oh, you were asking about pushstate. No, that specifically fixes the problem with the double fetch, so long as the server side and client side do the right thing to make the user see the same page for the same URL.
Pushstate just lets the JS client modify the URL without triggering a page reload, so the client can change the actual query param instead of the hash.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by TazeTSchnitzel on Monday January 09, 2017 @06:05AM
(#13355475)
Not unless the server doesn't interpret the URL the same way.