Incremental improvement is great, but I do want to know what they're thinking here.

They didn't mention it in the blog post that multiple isn't supported. Its perfectly fine if it is not supported right now. It would be great if they acknowledged that up front to set expectations accordingly.

For instance, if its explicitly not supported, then I won't be left wondering if its a bug or a misunderstanding of the implementation etc.

Communication would be really good here. I'm all for incremental improvement, I think we need more of it.

Doesn't mean there shouldn't be better communication about it.

In the original dev blog from last year they mention it’s still a work in progress.

https://developer.chrome.com/blog/rfc-customizable-select

> Note: The multiple and size attributes on select (<select multiple> and <select size=n>) are not supported in appearance: base-select yet.

From last year while it was a WIP

and now this as of Chrome 135 is shipped, and they didn't think it wise to include a back reference to this post, calling out what isn't supported?

They can and should communicate this is all.

Agreed. Should have mentioned it in this post or at least linked back to my source.