4 ms·
Did they also remove link wrapping with this? The HREF goes straight to the destination for me now on Chrome, where previously it went to some Google domain red
by patmcguire 7y ago
Did they also remove link wrapping with this? The HREF goes straight to the destination for me now on Chrome, where previously it went to some Google domain redirect. It's there on the first HTML load too, it's not a JS thing after the fact. Is there a different response for Lynx or are they formatting it in such a way that Lynx doesn't pick it up?
- Avery3R 7y agoThey're using the ping property of the <a> element now, the only good thing to come out of this
- e12e 7y agoHm, so now I can go straight to the Google hosted AMP version without bumping through Google an extra time first? /s
- e12e 7y agoOn a more substantial note, that's documented here: https://www.w3.org/TR/2008/WD-html5-20080122/#hyperlink0 https://www.w3.org/TR/2008/WD-html5-20080122/#hyperlink0 It's a little odd, to see that a browser "must parse", but also "may either ignore the ping attribute altogether, or selectively ignore URIs". It strikes me as a bit clumsy compared to the typical MUST/SHOULD/MAY wording. Anyone (other than Google) using a-pings?
- patmcguire 7y agoAh yeah that's definitely going to be different HTML on Lynx, then, since I bet they don't support that and Google's not missing out on tracking. Yup - curling with Lynx user agent gets a targets of href="/url?q=<whatever>" rather than href="<whatever>" ping="tracking"