Uhhh, press f5 every now and then? I'm very new to this haha
-
-
Replying to @yoshuawuyts
I'm too deep in the weeds now to make any objective opinions
1 reply 0 retweets 1 like -
Replying to @TatumCreative
Something FF could do better than chrome is have a good view on small screens. It was def not built with my 11" in mind
2 replies 0 retweets 1 like -
Replying to @yoshuawuyts
Although we're still only focusing on internal engineers for this tool at the moment.
1 reply 0 retweets 0 likes -
Replying to @TatumCreative
Lmk if you want a test drive of anything. Happy to share a scrappy framework engineer's perspectice of things :P
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
Which FF has very different performance characteristics compared to Chrome, so it's nice to try out on diff implementations.
2 replies 0 retweets 1 like -
Replying to @TatumCreative
just tried it out - biggest question I have is: how do I view frame duration? Chrome is super explicit about long frames and the like
3 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
We have an open bug on that. We need a sidebar and tooltips, but I have a few more data sources to expose first.
1 reply 0 retweets 1 like -
Replying to @TatumCreative
cool! looking forward to the changes - another thing I was missing was user timings, but guess those have not been forgotten haha :D
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Yup, definitely a to-do! It's lower priority for our engineers as they generally don't have that info when debugging sites in the wild.
1 reply 0 retweets 1 like
haha, guess it's on us framework engineers to fix that then :P
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.