what do the @w3c have to say about this? or are we at the point where google dictate the standarts?
-
-
-
It’s all linked in the Intent email. All other browsers are on board with this decision. FF: https://github.com/mozilla/standards-positions/issues/202#issuecomment-558294095 … Edge: https://twitter.com/_scottlow/status/1206831008261132289 … Safari already froze it’s UA:https://twitter.com/rmondello/status/943545865204989953 …
- Još 4 druga odgovora
Novi razgovor -
-
-
@betaorbust I imagine you all have seen but JUST IN CASE -
“The opt-in based mechanism of Client Hints suffers from the fact that on the very-first view, the browser has not yet received the opt-in. [...] We are exploring options to enable the opt-in to happen further down the stack to avoid that delay.” But like.. gonna break it first.
- Još 1 odgovor
Novi razgovor -
-
-
Recently we faced an issue, where service worker was failing the network requests made inside Webview in chrome 75, since there was a bug due to some experimentation in chrome. To solve this issue, we had to disable SW in chrome 75.https://dev.to/devteam/a-bug-in-chrome-75-caused-random-offline-pages-4jii …
-
Client hints can only tell which features are available in the browser, but what if there is a bug in one of those feature in some chrome version, Web Devs won’t even know in which version of browser that feature is buggy. 1/2
- Još 1 odgovor
Novi razgovor -
-
-
why not just stop sending the header?
- Još 4 druga odgovora
Novi razgovor -
-
-
I think this is a good idea, but at this stage very problematic and needs some serious fleshing out. My thoughts/concerns herehttps://github.com/WICG/ua-client-hints/issues/14 …
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
If you’re using UA as a means of feature detection you should just resign.
-
Even disregarding feature detection, UA parsing is still extremely common for analytics purposes (eg. tracking which browsers are used on a site).
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.