eeeps

zachleat, 1 month ago to random

I too would like to announce that I am not on the bluesky board of directors

zachleat, 1 month ago (edited 27 days ago) to random

Planning on doing a full #11tyConf Organizer retrospective blog post, but in the interest of transparency here’s a peek at the conference budget (funded primarily by our Open Collective, prices in USD):

Expenses: $7574.20
Revenue: $4653.79 (Free event, but via sponsors and merch)
Profit: -$2920.41

Edit: Fixed a spreadsheet error 😬

eeeps, 9 months ago to random

View Transitions Break Incremental Rendering https://ericportis.com/posts/2023/view-transitions-break-incremental-rendering/

chriscoyier, 1 month ago to random

Maybe we can get an interesting thread of examples here.

Less than 10 second videos of @container queries in action on websites.

Go!

eeeps, 1 month ago to random

h/t @Meyerweb

A TikTok reaction video that has had some text overlayed. A person (labelled "me watching React devs") watches someone else's hand put a series of shaped blocks into shaped holes. The holes and shapes are all basic and recognizable: square, triangle, circle, etc. The holes are labelled after HTML elements: "div", "button", "li", "table", "input" and "a". The hand takes a square block, which is labelled "generic block content"; The person excitedly says "square hole" (which is labelled "div") and is excited when that's where it goes. The hand then picks up a longer square block (labelled "element group"); the person also gets this one correct (also goes in the div hole), and is excited. The hand then picks up "tabular data"; the person wants it to go in the "table" hole, but no, the hand says it goes in the "div" hole as well. Person gets increasingly upset as blocks labelled "list item", "perform an action", "user input", and ultimately, "a hyperlink" all go in the "div" hole, and not the more appropriately shaped holes/elements that they are correctly calling out, each time, at the end – when "a hyperlink" goes into the "div" hole instead of into the "a" hole – almost though tears.

eeeps, 3 months ago to random

📝 I wrote a thing about color spaces in general and oklab()/oklch() in particular.

https://ericportis.com/posts/2024/okay-color-spaces/

zachleat, 10 days ago to random

is your tech stack a metaphorical cybertruck trunk slowly closing on your fingers? in this ted talk I will…

eeeps, 1 month ago to random

Am I missing something or is there no RSS feed for https://web.dev ?

eeeps, 4 months ago to random

@mia @bkardell Re: https://www.igalia.com/chats/a-lighter-shade-of-dom, when Miriam made the connection to Cascade Layers, I was like, "of course!" I haven't worked out what the solution is, but it has to start there I think?!

My mind goes to components being able to "export" layers, but it's more like, exporting to new origins?? And you'd need two slots – one with more power than authors (by default) for the "video chrome" use case and one with less for the "regular-ass-button" use case.

eeeps, 4 months ago to random

Hey so, if you want to put an AVIF in an SVG with a PNG fallback — how would you... do that?

alexcox, 30 days ago to random

I wish we lived in a universe where Apple apologized via a Notes.app screenshot.

nhoizey, 21 days ago to random French

“New field insights for debugging INP” by Jeremy Wagner

🔗 https://www.youtube.com/watch?v=xfjumh8ySRY

> Interaction to Next Paint (INP) is a Core Web Vital that measures how responsive a page is to interactions. Due to INP's scope, it can be difficult to identify why some interactions are slow. Learn how to use new Chrome APIs that provide detailed information on the causes behind slow interactions, and how to collect insights from your website's…

#INP #WebPerf #CoreWebVitals

⚓️ https://nicolas-hoizey.com/links/2024/05/20/new-field-insights-for-debugging-inp/

eeeps, 6 days ago to random

My wife, last week: “Why is your phone open to a note that just says, ‘Endless Shrimp Jesus?’“

Well!

https://ericportis.com/posts/2024/endless-shrimp-jesus/

eeeps, 1 year ago to random

I spy with my little eye... JPEG XL support coming to Safari!

eeeps, 3 months ago to random

https://salt-nlp.github.io/Design2Code/

eeeps, 7 months ago to random

https://docs.google.com/presentation/d/1oEaW5dn7sTko7GdyqaJ_-meEfHLguG__nLDeWla58A8/ from @tunetheweb is great. But it makes me wonder how I should be thinking about the “do work ahead of time” vs “don’t do speculative work you might not need” tradeoff these days. I’ve traditionally been a bit allergic to doing anything I’m not ~certain the user is going to need later.

eeeps, 2 months ago to random

Me, AirDropping a screenshot of a PDF to my computer so I can hold my phone up to it: ”Why can't I just click on the QR code?“

eeeps, 3 months ago to random

Probably bad idea: gamifying alt text generation with https://fastsdxl.ai. Can you get it to re-create your image? More or less?

> A summer day at Artist's Point at the Mt Baker Ski area. A brindle adult Plott Hound is sitting, amidst some Douglas Firs and wildflowers, facing the camera. Mt. Baker in the background.

An actual photo of my actual dog, described above. Looks real, because it is.

lene, 1 month ago to random

A possum contribution from my daughter #11tyconf

eeeps, 5 months ago to random

Oh dang custom states for custom elements are happening! Landed in the spec; they're also apparently shipping in WebKit, and are being worked on in the other two browsers. https://github.com/whatwg/html/pull/8467

My first reaction was: does this open up any new capabilities that you can't already hack together by toggling class names or data-attributes? My second: it seems important for custom elements to be able to define and exclusively control their own states; classes and attributes can be set by anybody.

eeeps, 4 months ago to random

Bobson Dugnutt followed you. Sleve McDichael followed you.

eeeps, 2 months ago to random

“CSS is so good these days!”

We owe lot of that goodness to work proposed, pushed, and/or led by @mia. Someone decided to stop funding her work. Let’s keep a good thing going:

https://front-end.social/@mia/112208118572767469

eeeps, 1 month ago to random

Converting an sRGB color to P3 does not make it “pop”. It doesn't change it at all.

If you want to make it pop, do so by boosting the chroma in a space like OKLCH. P3 does give you more room to boost.

https://observablehq.com/d/c09ce2e69591f709