iiinova — where your digital self keeps evolving

Cory LaViska @cory.laviska.com · 1h

yea wish the “from” was optional but still way better

000

Cory LaViska @cory.laviska.com · 5h

MDN docs: developer.mozilla.org/en-US/docs/W...

000

Cory LaViska @cory.laviska.com · 5h

I use `color-mix(in srgb, red 50%, transparent)` for mixing alpha in CSS but thrilled to see the new alpha() is baseline 2026!

240

Cory LaViska @cory.laviska.com · 6h

Most common case is probably icon buttons, as it gives users desktop more confidence in what they're about to click. My biggest gripe about title is a) style and b) show delay. Programmatic use cases and non-interactive HTML content can probably be handled fine with a popover, bth.

110

Cory LaViska @cory.laviska.com · 6h

I guess this would be nice for simple cases, but title tooltips have a too long hover delay, can’t be programmatically shown, and don’t support [non-interactive] HTML. So for most implementations, I’m still reaching for a component.

110

Cory LaViska @cory.laviska.com · 28/09/2026

just found the holy grail of iframe sizing in a Chrome update "Chrome 154 adds support for responsively-sized iframes, letting an <iframe> element in a parent document size itself to the embedded document…" developer.chrome.com/blog/new-in-...

developer.chrome.com

New in Chrome 154 | Blog | Chrome for Developers

Responsively-sized iframes, CSS scroll-marker-group modes, and CSS text-decoration-inset.

1130

Cory LaViska @cory.laviska.com · 27/09/2026

“It’s not coffee, it’s tea.” When can you start?

041

Cory LaViska @cory.laviska.com · 25/09/2026

Me neither. Who’s steering this ship anyways?

010

Cory LaViska @cory.laviska.com · 25/09/2026

But it’s different. And they’re all HTML elements so why treat them differently?

110

Cory LaViska @cory.laviska.com · 25/09/2026

It’s not too late to make native elements styleable with shadow DOM. They say it’s too late but I refuse to believe it 🌶️

120

Cory LaViska @cory.laviska.com · 25/09/2026

what a time to be alive not sure if that's sarcasm or excitement though

010

Cory LaViska @cory.laviska.com · 25/09/2026

It's a good dashboard/app element but I think meter's problem is awareness.

150

Cory LaViska @cory.laviska.com · 25/09/2026

seeing a lot of emails from companies I haven't logged into or subscribed to in years suddenly appear in my inbox my hunch is that they're trying to drum up business because traffic is falling likely due to AI anyone seeing the same thing?

130

Cory LaViska @cory.laviska.com · 25/09/2026

An honor, sir! Can’t wait to do it again. If you’re in the design system space, give @michaelwarren.dev a follow.

042

Cory LaViska @cory.laviska.com · 24/09/2026

And if businesses think it produces faster results, which it does, and if those results are even somewhat close to what a human would produce (as measured by result — did it ship? Does it mostly work?) it’s not going away.

000

Cory LaViska @cory.laviska.com · 24/09/2026

Prohibition took something away that people wanted. AI is giving people something they want. The tool is not going away and people are inevitably going to continue to use it.

200

Cory LaViska @cory.laviska.com · 24/09/2026

"Acceptance is really misunderstood because acceptance can be misinterpreted as, 'Oh, suddenly I'm cool with all of the downsides, all of the harms, all of the risks around this technology.'" 🎯 by @bradfrost.com bradfrost.com/blog/post/gr...

bradfrost.com

Grief in the AI Age

I'm Brad Frost, an independent creator, web designer & developer, teacher, speaker, writer, musician, and artist based in Pittsburgh, PA.

152

Cory LaViska @cory.laviska.com · 24/09/2026

I knew some of them but never imagined it would work for the thing I actually needed 😅

010

Cory LaViska @cory.laviska.com · 23/09/2026

Looks like Interop 2027 proposals close today. Got a web platform gap that still burns (CSS, a11y, web components)? File or boost an issue before the window shuts. webkit.org/blog/18283/s...

webkit.org

Submit your ideas for Interop 2027

It’s that exciting time of year again when we start considering Interop proposals for next year!

153

Cory LaViska @cory.laviska.com · 23/09/2026

i keep discovering things I probably should have know for years, like pressing OPTION to copy a file's pathname way easier than get info > select pathname > copy

Screenshot of a desktop icon's context menu, highlighting Copy "test.html" as Pathname which shows when you press option

4261

Cory LaViska @cory.laviska.com · 23/09/2026

Claude doesn’t work for free 😅

010

Cory LaViska @cory.laviska.com · 22/09/2026

I don't miss Sass, I miss named breakpoints. We can almost get there with raw CSS. 🤏 www.abeautifulsite.net/posts/named-...

:root {
--viewport: 'desktop';

@media (max-width: 64em) {
--viewport: 'tablet';
}

@media (max-width: 37.5em) {
--viewport: 'mobile';
}
}

@container style(--viewport: 'mobile') {
/* Styles for the mobile bucket */
}

5707

Cory LaViska @cory.laviska.com · 22/09/2026

For the right apps, merging CSS is the only sane way to maintain it. Good call

000

Cory LaViska @cory.laviska.com · 22/09/2026

I’m team semicolon and curly but that’s a valid reason 😄

010

Cory LaViska @cory.laviska.com · 22/09/2026

instead of skills to pay the bills, now we have bills to pay the skills

1100

Cory LaViska @cory.laviska.com · 18/09/2026

Interesting use case. Whats the shelf life of those boards?

100

Cory LaViska @cory.laviska.com · 18/09/2026

The icon is cached the first time its requested, so a dozen ratings won't load the icon from the server 12 times :)

100

Cory LaViska @cory.laviska.com · 17/09/2026

That’s definitely one thing CSS can’t do on its own 🥲

100

Cory LaViska @cory.laviska.com · 17/09/2026

Any idea why neither of these have landed cross browser? And why the other browsers adopted WebKit’s syntax for line clamp?

110

Cory LaViska @cory.laviska.com · 17/09/2026

That’s great! And yes, customizable break points would have been nice when custom properties landed.

000

Cory LaViska @cory.laviska.com · 17/09/2026

I don’t think there’s a rule. Do what feels good and what remains readable. I frequently use nesting to scope things to a class or container.

010

Cory LaViska @cory.laviska.com · 17/09/2026

Same tbh. Although it was kinda painful until nesting was widely supported. CSS is in a great place these days!

140

Cory LaViska @cory.laviska.com · 17/09/2026

It’s fair game! Appreciate the link

020

Cory LaViska @cory.laviska.com · 17/09/2026

I recently had to convert a legacy Sass project to CSS and it felt so good to have one less step 😅

010

Cory LaViska @cory.laviska.com · 17/09/2026

Is that similar to PostCSS but in rust?

110

Cory LaViska @cory.laviska.com · 17/09/2026

Nice. CSS is so powerful now!

000

Reposted by Cory LaViska

Joe Dakroub @dakroub.co · 16/09/2026

The `wa-tag-input` is terrific and much-needed. Thank you all for your hard work on the best component library there is!

141

Cory LaViska @cory.laviska.com · 17/09/2026

I haven't used Sass or Less for years now that CSS nesting and CSS custom properties exist. Has anyone else gone CSS-only? (yes I know preprocessors do more, but this is all I usually want from them)

15180

Cory LaViska @cory.laviska.com · 17/09/2026

wait you can swipe left/right on the address bar in iOS safari to switch tabs? TIL

220

Reposted by Cory LaViska

Web Awesome @webawesome.com · 16/09/2026

Tag, you're it! 🏷️ Web Awesome 3.13 is out. The new experimental <wa-tag-input> turns keywords, emails, and labels into tidy, removable tags. We also fixed up the data grid and promoted 11 components to stable. webawesome.com/docs/resourc...

webawesome.com

Changelog | Web Awesome

Changes to each version of the project are documented here.

273

Reposted by Cory LaViska

Zach Leatherman @zachleat.com · 16/09/2026

For reusable components: has anyone stress tested the seams around Light versus Shadow DOM? Hypothetically: 20 light DOM nodes per instance versus 1 light DOM node (with 19 shadow DOM nodes) per instance. 40 vs. 1+39? and instances? I don’t think I have a baseline intuition on the costs there.

4122

Cory LaViska @cory.laviska.com · 16/09/2026

We do see a lot of repeat contributors and that builds trust overtime, but I worry about bad actors playing the long game and eventually shipping vulnerable code with that trust. The review struggle is real.

030