Joe Shelby

looks like they kind of blurred the idea of menu and select a bit (not the first time they've tried to consolidate components that have different historical legacies and needs)....

yeah, i think this one's right. see https://material-web.dev/components/button/

Replicated. Looks like the button is still listening for the key events, so either the input needs to stop propagation on a keystroke or the button needs to know that...

The Spec of [material-expressive](https://m3.material.io/components/text-fields/overview) calls for 16px in all of its examples. However, I do see BeerCSS has a 'bug' in that it has 16px to the left of the...

The 'theme' one returns a promise, so you can 'await' it in an async (or promise-chain, but awaits are better) in order for one to finish before calling the other.

Just a philosophical/tech question - why non-module when the direction of JS increasingly is for modules to the point that ES6 is eventually going to be 100% universal, even more...

The CDN does attach it to window['ui'], so that part's already taken care of. ( _context.ui = _ui; where _ui is beercss and _context is globalThis...BUT, see last paragraph below)...

The build system uses vite +. vite likely has some UMD configuration support somewhere in it. I may give that a try later today and see what the resultant file...

nothing I can do without patching things will magically turn the export into something that doesn't have an export command. at least not magically. i could probably do some hackery...

UPDATE. found it. in the rollup options. ``` import { build } from "vite"; export default async function() { try { await build({ build: { minify: false, type: 'umd', target:...