Mihira Jayasekera

ELON: AI poses an existential threat to humanity. SIRI:

@grigs @CloudFour Thanks so much for sharing! I've been wrapping my head around cumulative layout shift, `aspect-ratio`, etc., so your debrief is incredibly helpful. Really appreciate your candor and generosity to take the time to share! 🙏

@_tinymachine @CloudFour So when you raised the issue, the most vivid memory I have is of resizing the browser to pick the correct breakpoint for the <picture> element. I forgot I added the attributes late. The real solution is making sure the next version of the site handles height and width.

@CloudFour Hi there, I noticed that some of your recent blog posts have images that get compressed horizontally on narrower viewports. I'm sure you know, but I think adding `height: auto` should fix this?

@grigs @CloudFour My pleasure - thanks for all the invaluable knowledge you and your team shares! If not too much trouble, can you let me know what happened if you get to the bottom of it? Just curious from a workflow standpoint!

@_tinymachine @CloudFour Fixed for now. I’m confused about what happened. Thanks for letting us know.

@forestryio Read-only content in the sidebar is great, but could there also be read-only fields (like an 'instructions' field) in front matter templates? Would be useful for providing page-specific help text to editors right in the context of editing a page.

Applies to product design too. The user’s mental model is the product. Not the flows, not the UI.

@backblaze In the B2 docs (backblaze.com/b2/docs/bucket…) it looks like the units for max-age for cache control are half-seconds (5 minutes, `max-age=600`). The 'such as' adds ambiguity, but I'm guessing you meant either 10 minutes or `max-age=300`?

@SlackHQ Thanks for the update!

@_tinymachine Hey there, we're afraid we don't have an ETA to share on when P3 will be fully supported but we know there is interest in this and it's something we're keeping in mind. Thank you for your patience in the meantime!

Why does @SlackHQ desaturate photos you upload into it?

@SlackHQ @ThisIsPizza It looks like Slack iOS and desktop Mac apps still aren’t displaying images with embedded Display P3 profiles accurately. (Slack in Safari and Chrome seem to display them just fine.) Any timeline on when P3 will be supported in the standalone apps?

@ThisIsPizza Thanks for clearing that up, Adam. We do apply some compression for the in-channel preview that would affect saturation in this way, but we'll add a note for the team here that this isn't working as well as it could for you. 📝

@JoshWComeau Dad jokes + CSS = my sweet spot (for better or worse!)

@JoshWComeau CSS positioning usually makes me cry, but this made me laugh out loud 😂

@upstatement Big fan! Think I spotted a typo in your MIT.edu write-up — I think you meant 'complement'.

@PranavDixit I'm sure meant no harm, but calling people without disabilities "regular" can be alienating to people with disabilities. Google has some recommendations here: #about-disability-and-accessibility" target="_blank" rel="nofollow noopener">developers.google.com/style/inclusiv…

This is insanely cool. Apple presents this as something for disabled people, but I can totally see regular people using this too.

'Check status' indeed. Unexpected results (profile pic notwithstanding).

@leebert Wow, sounds great! Let me know if I can be of help. (I do a bit of React and vanilla JS coding, but want to get my feet wet with TypeScript and Figma plugin dev, in case there’s some grunt work you could use some help with.)

@_tinymachine I’m thinking about doing a complete redesign for 2.0 to make it more functional…live preview, custom path names, direct export options, etc…I will add this to the list 👍

@leebert Thanks for sharing your Figma plugin Design Tokenizer; it looks great, but I was just trying it out and noticed exported hex values for color styles didn't match what was spec'd in Figma (e.g. #0098FF exported as #0076c6, #FFA000 exported as #ffeccc). Any ideas why? Bug?

@leebert …so maybe that’s not really workable unless you introduced an option for flattening the hierarchy, which I know you might not want to do.

@_tinymachine I ran a test on my machine and was not able to reproduce the bug. Can you provide me with any additional info?

@leebert Oh, come to think of it, for my particular use case, it would be preferable to flatten the hierarchy for everything under “color”. (So the keys would be “Primary/Blue#0098FF” and then “Primary/Blue#0098FF/Light#28C0FF”.) That would break current behavior of plugin, though…

@leebert Thanks for looking in this! I think I've isolated the issue: I'm using some nested styles in my file, similar to screenshot below. It looks like the plugin doesn't correctly handle styles nested in this (admittedly kinda weird) way — only one value is getting exported.

@erikdkennedy Your Font Sizes in UI Design (learnui.design/blog/ultimate-…) is a great reference. One q: after explaining `sp` is intended for specifying font sizes, 2nd-to-last sentence says, 'For Android apps, just type “dp” into the box and call it a day.' Did you mean `sp` ?

@dotdude Nice use of FigJam btw 😉

I wrote some words around thoughts and experiences with branching in @figmadesign, and some scenarios where you may (or may not!) want to use them. Has anyone tried the beta yet? In what other scenarios would branching be beneficial?