• @jaffathecake Although now that I’m reading through caniuse it looks like it the only multi-vendor imp was the final one

    • 0
    • 0
  • @jaffathecake multiple implementations happening all following a standard and then that changing in non-compatible ways

    • 0
    • 0
  • @jaffathecake What concerns me about that definition is getting burned by something like flexbox again, but understand the goal

    • 0
    • 0
  • @jaffathecake Not that I don’t love what’s happening, just a question about how “standards” are understood.

    • 0
    • 0
  • @jaffathecake So if it’s only supported in Chrome? Or more extreme, only supported in Chrome and not on roadmap anywhere else?

    • 0
    • 0
  • #ChromeDevSummit Tough Question: Isn’t that a Google experiment at that point? Not a standard? 2/2

    • 0
    • 0
  • #ChromeDevSummit Tough Question: How does Google rectify saying things are open standards when only Google supports it and is in Draft? 1/2

    • 0
    • 1
  • @thealphanerd @Una @DogpatchJS cupertino. The CDS party is tonight!

    • 0
    • 0
  • How to deal with permissions with respect for your users. #ChromeDevSummit

    • 0
    • 3
  • The main security takeaway from #ChromeDevSummit is: you wanna do something besides send a user text? HTTPS. Even then, HTTPS.

    • 1
    • 1
  • RT @ChromiumDev: Physical Web is now available in Chrome DEV, hear more at the #ChromeDevSummit: g.co/chromedevsummit https://t.co/uF1BE…

    • 0
    • 0
  • RT @tkadlec: Awww yeaaaahh… #chromedevsummit @ThePhysicalWeb

    SO excited about this!

    • 0
    • 0
  • Web bluetooth, bluetooth device access from the web! #ChromeDevSummit

    • 0
    • 0
  • Internet of Things. #ChromeDevSummit

    • 0
    • 1
  • Send notifications that users care about. #ChromeDevSummit

    • 0
    • 0
  • @addyosmani @gauntface Us IBMers are sitting here, nodding, taking notes for things to bring back. This will be one of them.

    • 0
    • 3
  • RT @addyosmani: @Snugug and Mr. @gauntface :) It’s been fun playing with app shell techniques for the last few weeks 🎈

    • 0
    • 0
  • Vanilla JS app shell demo by @addyosmani for working with service workers. #ChromeDevSummit

    • 0
    • 1
  • Service workers need to be treated as progressive enhancement. First view will never have, same w/old browsers. #ChromeDevSummit

    • 0
    • 2
  • sw-toolbox can help maintain your cache with service works too. Super helpful. #ChromeDevSummit

    • 0
    • 0
  • Use sw-precache w/build system to automatically generate your service worker code w/update support #ChromeDevSummit

    • 1
    • 3
  • sw-precache and sw-toolbox are service worker libraries ready for production. #ChromeDevSummit

    • 0
    • 1
  • Grab bag of security best practices. #ChromeDevSummit

    • 0
    • 2
  • Content security policy header to rewrite insecure requests to secure ones (if available). #ChromeDevSummit

    • 0
    • 1
  • Content security policy header for getting notified for mixed security content. #ChromeDevSummit

    • 1
    • 1