Not necessarily. This is not specified behavior. Especially on Linux platforms, “native” is widely varying depending on your desktop theme. User Agents should not be responsible for needing to figure out native type styling and making it work in a web page. This kind of thing is buggy and error-prone. It is best that if developers are targeting a platform specifically and want native styling, they handle that in their application. Web standards also don’t provide all the UX components covered in these component libraries, so what should be done there? We invent new specs to cover every component possible?
The Extensible Web Manifesto guides us into thinking more about low-level capability to enable new functionality in the web that currently isn’t possible or is extremely difficult to get done on the web. Native-like styling doesn’t fit this bill. It is entirely possible. The difficult part is adapting on-the-fly to various OS types, but it’s completely possible as well someone just needs to put the effort into making a component library aimed at doing that seamlessly.
I don’t feel this request meets the bar as something that the web community should be pushing for in User Agents/standards. We have much more interesting targets that unlock new capabilities that should be looked into and pushed. Rather than pushing for something that is rehashing a debate from the dawn of the web which doesn’t have a good solution for UA’s. It’s a big time sink for them to maintain and fix bugs. Maintainer time is best spent elsewhere from my point of view.