Not defending this particular library, but there are some good reasons to use React abstractions even for simple things like a button. Some examples: * If the

Not defending this particular library, but there are some good reasons to use React abstractions even for simple things like a button. Some examples: * If the form deals with state and validation, then <Button> (as opposed to <button>) can automatically disable itself if the form's input isn't valid. * It can incorporate useful features like preventing redundant clicks (to prevent duplicate submits) and showing submit progress (eg., replace button label with a spinner while it's pending). * You can more easily add features that you would have to manually wire with an HTML <button>: For example, let it take a "tooltip" prop that will automatically show a tooltip on hover. As an aside, I should add that I wouldn't code up a "form with submit and cancel" like this. I would have the form component itself render the submit and cancel buttons, and call it something like SubmittableForm. This way, it can be in control of the UI (eg., validation, button placement, etc.) and submit logic. As for that htmlFor thing, I don't know why this library does it that way. There's no reason it couldn't correctly wire up a "for" attribute itself on the HTML label element.