3 ms·
so, they're actually just removing the option for websites that use still use a /#! url structure to send a pre-rendered copy of the page. not quite the same t
by notatoad 9y ago
so, they're actually just removing the option for websites that use still use a /#! url structure to send a pre-rendered copy of the page.
not quite the same thing as abandoning ajax crawling.
- lmkg 9y agoThey are abandoning the ajax crawling scheme. "Scheme" in this case in the sense of "documented interface," not in the sense of "we plan to do things." Easy confusion though, since the scheme didn't see much uptake that I'm aware of.
- _sdegutis 9y agoGood thing they aren't abandoning AJAX Crawling Scheme support though. Specialized lisp dialects are the lifeblood of our industry.
- hhbbhhg 9y agoAre you some kind of idiot?
- hamandcheese 9y agoYour joke is either not well received or over peoples heads, but I chuckled.
- deleted 9y ago[deleted]
- Phrodo_00 9y agoWebsites have never really had the option to send prerendered content on /#! urls, since the part after # is not sent to the server. Closest thing would be to have javascript request a prerendered view from another url and replace the current view, but that doesn't sound useful.
- gpvos 9y agoI think that is what they mean with the ?_escaped_fragment_= URLs: they defined a way to map the #! URLs to URLs that could be sent to the server to get a prerendered page. But I may have guessed wrong, I don't really know.