RT @HenriHelvetica: Great lightning talk during #ChromeDevSummit from @tomayac on dark mode. Been looking for more explainers. Glad you’re…
igrigorik Nice thanksgiving present.. Support for Server Timing is now available in Firefox Nightly DevTools!
What’s Server Timing? @smashingmag has a nice nice intro tutorial: bit.ly/2CS1bMY pic.twitter.com/1NdvzCjX43
RT @FlowBrowser: Flow is a new clean-room multithreaded browser. Today it reached a new milestone: Rendering full Google Mail. https://t.co…
This is a good thread on first- vs. third-party cookies and recent blocking circumventions: https://t.co/cYL53HFZaw. https://t.co/tJriRhiwZ1
@kennethrohde @slightlylate Just recalled that they’re a Google company now: https://t.co/KzKblaTBMz. Might be helpful in the causa Project Fugu 🡠given all their sensors APIs.
(CC: @fractorious.)
@derSchepp @ChromiumDev @ChromeDevTools I *think* we don’t do this on purpose, but @slightlylate is better suited to address this proposal.
For combining tokens: you can combine them in one HTTP header separated by comma: https://t.co/1eML2pwVUt.
@derSchepp @ChromiumDev @ChromeDevTools Each token needs to be in its own meta tag.
@derSchepp @ChromiumDev @ChromeDevTools In @ChromeDevTools you can check for the presence of OTs via `$$(‘meta[http-equiv=”origin-trial”]’)`, but you can’t see which OT the tag is for. You can, however, feature-detect all current OT APIs (https://t.co/W6L