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. Scott Jehl‏ @scottjehl Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @Paul_Kinlan @jyasskin

      I see both sides. The low-level tools are great, but feel complicated for common patterns. It's become pretty routine to use say, int. observers all over a site to achieve what CSS should offer as a pseudo-class (eg ":stuck"). My worry is when efficient is viewed as good enough.

      2 replies 0 retweets 4 likes
    2. Scott Jehl‏ @scottjehl Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @scottjehl @slightlylate and

      (forgive me if there's progress on "stuck" in particular (that'd be great)... it's more of a comment on similar common patterns like accordions, tabs, stuff like that that we build differently every time, never knowing how to wire it up quite right for a11y)

      1 reply 0 retweets 1 like
    3. Alex Russell‏ @slightlylate Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @scottjehl @Paul_Kinlan @jyasskin

      One of the reasons we need to provide outgasses is that it takes *so long* for groups like CSSWG to make progress, and it's hard to judge how important a specific feature is. One of the goals of making the "hacks" more system-supported is to create semantic transparency.

      2 replies 0 retweets 1 like
    4. Scott Jehl‏ @scottjehl Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @Paul_Kinlan @jyasskin

      yeah. Still there are a handful of features that I think are widely mentioned as needed and missing, and are unlikely to prove out that way. I'm not going to build a production design system that relies on resize observers, but I certainly still want container queries in CSS.

      1 reply 0 retweets 4 likes
    5. Alex Russell‏ @slightlylate Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @scottjehl @Paul_Kinlan @jyasskin

      I'm optimistic about some of the work browser teams are doing now to better survey developers to get a better data-driven understanding of what should be tackled. In all cases, our goal w/ Blink is to move these sorts of decisions to a more evidentiary basis.

      1 reply 0 retweets 3 likes
    6. Alex Russell‏ @slightlylate Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @scottjehl and

      ...but even with perfect prioritisation, bandwidth isn't there to solve all needs in declarative-land. Will continue to need escape valves, and they shouldn't make live *fundamentally* worse for end-users because devs got stuck somewhere.

      1 reply 0 retweets 1 like
    7. Scott Jehl‏ @scottjehl Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @Paul_Kinlan @jyasskin

      I guess I'm unclear on how to show evidence of a pattern I want to use when I'm not going to build an approximated version of it that relies on JS APIs. I'd rather build with the less ideal existing alternative. Hard to use the production web as a proving ground for experiments

      2 replies 0 retweets 4 likes
    8. Alex Russell‏ @slightlylate Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @scottjehl @Paul_Kinlan @jyasskin

      The production web has always been our proving ground. If something is important enough to ship a hack for, it means browsers have more work todo. We cannot evolve through speculation.

      1 reply 0 retweets 0 likes
    9. Scott Jehl‏ @scottjehl Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @Paul_Kinlan @jyasskin

      I think that makes sense in some cases. But it seems like it could be biased against developers who will choose an inconvenient but reliable tool over an approximated, hacked together future API for a large-scale site every time. And they may be the ones who need to be heard most

      3 replies 0 retweets 2 likes
    10. Alex Russell‏ @slightlylate Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @scottjehl @Paul_Kinlan @jyasskin

      Totally agree that we have a pretty bad selection bias problem right now. Injecting data from developer behavior has helped shift us away from smoke-filled-room navel gazing, but shifting the focus to framework authors has similar downsides (self-preservation key among them).

      2 replies 0 retweets 1 like
      Alex Russell‏ @slightlylate Apr 7
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @scottjehl and

      So the important thing is to challenge the evidence with *better* evidence, rather than retreat back to a less evidence-based status-quo.

      10:07 AM - 7 Apr 2020
      • 2 Likes
      • Bridget Stewart Scott Jehl
      0 replies 0 retweets 2 likes

      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