-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think Reza's recap pretty much covers it.
With regard to resolution for desktops, I agree. I would even go a step further : unless the API client specifically requests it [cfr W3C API] *not* to include any 'default' values. The reason being : the API client cannot tell a 'default' from an actual value. A missing value on the other hand would allow the client the option to implement a default they know and which makes sense in their current context. And I too see an increase in demand, in my case mainly on the analytics side as more sites are wondering : is my responsive stuff actually 'reaching' the right devices ? Before I go to my meeting with Mr.Sandman : UserAgents. Get as many as possible, but 1st and foremost get at least 1 for every device in the repository. esjr -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJT2F8WAAoJEOxywXcFLKYc36IH/RmXzZarB00ThIDFtHFZ3J8k zbACwTF3DLNaXyNBMmEmAbGoVmc0IH2GyaMXH2Fp+yTP+iYjHPub+ODEw7oiyxji aCYwfQ4CA4iMssnFa4VP3GayvUrrw14GzIqBjK8piuaeQkayXVynB8hnYdzYc6Xx AHcesAxFXUDPYfg1gzK0HaMdP8KtrzO6vJ4YKUi7cy8et7z4yDwd0esLrKcEGU4f hlLMIQI97yu5/QtYhxSXEcFHPLeh1u+6MNBngcCFRhjYsuy9qOzr6scb51PgM0zU K7Q2KKrqUnCHY/Qh/g/6KiRqwlbMeJ0zSpt+TkkepNIUc4GODJJypG/pe1KNK5g= =qdYN -----END PGP SIGNATURE-----
