> Many of them the site is going to have to know for the page to even render properly Which illustrates that something has gone very wrong in the logical divis

> Many of them the site is going to have to know for the page to even render properly Which illustrates that something has gone very wrong in the logical division between "the site" and "the user agent". Technically, the site has no business asking about screen resolution, cache status or installed fonts etc That is information which should be relevant only to the user agent in constructing the view for the user. But browsers do not make a distinction between rendering-domain data and those data which do validly dictate what functionality the site provides to the user agent. Except for location, which is somehow perceived as sacred. Which brings us back to the original question; why are all the data elements thrown into the general Javascript bucket and made fair game for grabbing, except location data? Why not draw the boundary around data that should be private to the user agent? The user should never be interrupted by a prompt to share a list install fonts because, frankly, that information should never be divulged.