Original description:
Much like the issues described in FKAMP-2, we still get AMP pages served (from Google's cache) when visiting news stories linked to from new.google.co.uk. Using "Request Desktop Site" resolves that to some extent, but Google seem to have opted not to use responsive design on Google News and instead rely on user-agent sniffing. So you wind up with a page that's formatted for a widescreen monitor.
Means, half the time, important images are missing from the news stories and they're rendered otherwise pointless.
Need to look at whether the existing Google search centric script is directly applicable to Google News, or, failing that, at implementing a new script to get rid of AMP.
Google News is horrendously AMPy, but just like in their search results isn't declared as AMP in the markup. Unlike in their search results, they're also not using the
canonical correctly and simply declare themselves as being canonical (so you can't even auto-follow to a proper page).
This issue implements a new user script
redirect_to_non_amp_sites.user.js to handle similarly hostile pages by redirecting known bad domains to another domain that provides similar functionality without the AMP baggage. In this case, that's redirecting Google News to Bing news.
Activity
2019-06-09 13:02:10
On
AMPy U-A
Default UA
Although that page will show an AMP icon if AMP is considered acceptable for your device, the redirection to AMP content happens further down the line - If we look at the result of hitting those URLs both with and without a mobile UA the result is much the same:
If we follow the redirects, then one results in AMP content being served from new.google.co.uk:
The other results in us ultimately hitting the actual news site
2019-06-09 13:05:39
Worse, they are not actually providing an accurate canonical link
Following that link just sends us round the merry-go-round again as Google still redirect us back to the AMP content:
2019-06-09 13:13:43
If you load the page with a non-AMP UA, then switch the UA to be a mobile one and click the link, you end up being served a proper page rather than the AMP one.
Looking at it with Developer Tools, just like in FKAMP-2, what Google are actually doing is rewriting the page with Javascript and then updating the address bar.
2019-06-09 13:33:35
So, actually looking at the source for
To be honest, at this point I'm a little inclined to do the unthinkable and just have the script redirect Google News to Bing News (which doesn't currently have the same issue). Never thought I'd find myself actually preferring anything Bing to Google's offering....
2019-06-09 14:05:53
Webhook User-Agent
View Commit
2019-06-09 14:10:46
Webhook User-Agent
View Commit
2019-06-11 17:40:32
2019-06-11 17:40:32
2019-06-11 17:40:37