[dmarble]

  On Android Chrome with Data Saver turned on, elements with loading="auto" or 
  unset will also be lazily loaded if Chrome determines them to be good 
  candidates for lazy loading (according to heuristics).

I don't agree with this design decision to make the default ("or unset...") allow for lazy loading, even if limited to Data Saver enabled phones. Doesn't this mean every site on the planet that deems Android >= 7.0 web traffic important and makes use of pixel-based or iframe-enclosed tracking will have to go through testing and potential modification?