Using native control implementations in a browser isn't really an option. They make a lot of assumptions about how rendering works and how input events are routed which don't hold up inside a browser.
I guess the parent was referring to re-implementing them within the browser. In other words, not using the actual native one but creating a fake one that looks and behaves like the native one.
