opened
JoviDeCroock
username_0
We did not support having multiple `selected` attributes on `<option>` tags.
After evaluating this issue I saw that our compat missed the option to pass an array of values to `<select>`. This was made possible by the first fix.

Fixes: https://github.com/developit/preact/issues/761
(feature) - multi select support
issue
created
JoviDeCroock
username_0
I notice you are always adding the added bytesize, do you have an addon for this? Or you just check by hand? If you just check by hand I'll add it myself next time.

Allthough I don't think added bytesize is too important when it revolves around added support (correct me if I'm wrong)
comment
created
marvinhagemeister
username_1
@username_0 We don't have an automatic process for that. The number is taken from our build output. There we just compare it to the result you get in `master` and post the delta. We always use the first number at the top:

![preact-build](https://user-images.githubusercontent.com/1062408/54374597-c3b94280-467f-11e9-94ca-734f4175ca75.png)

It's more of a mental game. You'd be surprised how much all these little savings add up. It also helps being very aware of the size implications. There are cases where a PR may introduce a cool new feature, but the size increase is way more than it should be. In that case the team usually comes together and finds ways to rewrite the code to bring it down again. Having that culture is the secret sauce as to why we're still at 3kB despite adding tons of new features over time :tada:
comment
created
JoviDeCroock
username_0
Allright, will start paying attention to it in my next fixes/features. You all are very aware of the transpilation costs of things, that's so nice. Hope I can learn the same reflex, since sometimes I really can't see it. Trying to do it really pragmatic in my own OSS libraries but still got a lot to learn as you can see.
comment
created
jerry153fish
username_2
hello @username_0 is this feature going to preact as well in the future ?
comment