4 ms·
Interesting, so to be clear, the sequence looks like this: 1. User goes to website, UA communicates previously known features for this browser. 2. Browser doe
by spaceribs 7y ago
Interesting, so to be clear, the sequence looks like this:
1. User goes to website, UA communicates previously known features for this browser.
2. Browser does feature detection after load
3. Browser communicates any new browser features up to a backend service, crowd analysis determines if new features have been implemented for this UA.
If that's the case, that's a pretty awesome way of keying features, but I'd have to think about the implications in practice.
- mattnewton 7y agoNo, I haven’t seen anything that fancy. The “user” in step 1 is internal QA testing the site on the browser, maybe after seeing it a lot in logs. Exposing users to novel UA strings to a bunch of feature detection JavaScript is an interesting idea but it’s probably better to log them and then do this in a QA setting.
- finchisko 7y agolike this proposal