Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
slightlylate's profile
Alex Russell
Alex Russell
Alex Russell
@slightlylate

Tweets

Alex Russell

@slightlylate

Chrome Project 🐡 & Web Standards TL; Blink API OWNER Named PWAs w/ @phae; probably making her ☕ DMs open. Tweets my own; press@google.com for official comms.

San Francisco, The Internet
infrequently.org
Joined December 2010

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Manish‏ @ManishEarth 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      The proposal does have merit: it probably would be good for screen readers (though <dialog> or aria role=dialog probably suffices? maybe?) but that's not really front-and-center, it's "developers might get this wrong" (which is what libraries are for)

      2 replies 0 retweets 9 likes
      Show this thread
    2. Manish‏ @ManishEarth 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      to think Google pushed super hard on Custom Elements -- to the point of jumping the gun on shipping, ending up with an incompatible shipped version-- to not use it as the primary path for situations like these

      1 reply 1 retweet 25 likes
      Show this thread
    3. BrendanEich‏Verified account @BrendanEich 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ManishEarth

      I heard they always use flags to prevent forging de facto standards. Not in CE’s case?

      1 reply 0 retweets 1 like
    4. Manish‏ @ManishEarth 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BrendanEich

      I'm not sure exactly what happened; but "custom elements v0" got used quite a bit, especially on Google properties. YouTube was using v0 (with a slow polyfill for other browsers) for years after v1 shipped

      1 reply 1 retweet 3 likes
    5. BrendanEich‏Verified account @BrendanEich 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ManishEarth

      Tagging @erikcorry - seeking light not heat.

      1 reply 0 retweets 0 likes
    6. ᎬᎡᎥᏦ‏ @erikcorry 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BrendanEich @ManishEarth

      I don’t know the history of custom elements sorry, perhaps @slightlylate ?

      1 reply 0 retweets 0 likes
    7. Alex Russell‏ @slightlylate 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @erikcorry @BrendanEich @ManishEarth

      We shipped v0 Web Components in 2014 after multiple years of attempting to collaborate with basically everyone. Weren't many choices & hadn't yet invented Origin Trials (see blog post from '15: https://infrequently.org/2015/08/doing-science-on-the-web/ …)

      2 replies 1 retweet 7 likes
    8. Alex Russell‏ @slightlylate 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @erikcorry and

      My personal view (not shared by others) is that V0 shipping precipitated others coming to the table to do V1, which we pursued through '15, culminating in Safari and Chrome shipping V1 impls in '16 (Safari was first to their dev channel, we were first to stable)

      2 replies 0 retweets 6 likes
    9. Alex Russell‏ @slightlylate 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @erikcorry and

      Mozilla didn't ship a Web Components v1 impl until late '18:https://hacks.mozilla.org/2018/11/the-power-of-web-components/ …

      2 replies 0 retweets 0 likes
    10. Manish‏ @ManishEarth 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @erikcorry @BrendanEich

      Wasn't this in part due to compat issues caused by v0? We had similar problems with U2F -- Firefox got U2F support two years ago but couldn't ship it for quite a while because sites used Google's u2f.js which relied on implementation details.

      2 replies 0 retweets 3 likes
      Alex Russell‏ @slightlylate 14 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ManishEarth @erikcorry @BrendanEich

      V0 sites universally served polyfills. Those didn't interact with V1 (totally different API surface, by design). Mozilla seemingly just didn't put enough people on the project...IDK why.

      3:18 PM - 14 Jun 2019
      • 1 Like
      • Peter Burns
      1 reply 0 retweets 1 like
        1. Yehuda Katz  🥨‏Verified account @wycats 14 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @ManishEarth and

          🤔🤔🤔

          0 replies 0 retweets 1 like
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info