@slightlylate @igrigorik @JoeBeOne @ivanristic @wycats I dunno. Can't we just spend time fixing some of Chrome's many broken things first?
-
-
Replying to @sleevi_
@sleevi_ Imagine if you couldn't write reliable, automatic tests in blink. That's state of web platform.@slightlylate@igrigorik@wycats2 replies 0 retweets 2 likes -
Replying to @frgx
@frgx So we just gave up on WebDriver and friends then? Plenty of tools already exist in this space...@slightlylate@igrigorik@wycats3 replies 0 retweets 0 likes -
Replying to @sleevi_
@sleevi_ That's the disconnect: used to think so but try using WebDriver or writing tests for this stuff.@slightlylate@igrigorik@wycats1 reply 0 retweets 0 likes -
Replying to @frgx
@frgx Having reliable CI catching bugs in a 6-week framework release cycle means headless REAL browsers.@sleevi_@slightlylate@igrigorik2 replies 5 retweets 4 likes -
Replying to @wycats
@wycats exactly. For example, the Vine CSP Chrome crash could have been caught earlier :(@sleevi_@slightlylate@igrigorik2 replies 0 retweets 0 likes -
Replying to @frgx
@frgx And that is my point. That failure is on Chrome and its engineering practices, not lacking the shiny@wycats@slightlylate@igrigorik3 replies 0 retweets 0 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.