Comment by iaml

Using built-in html primitives seems like such a good idea in theory, but when you have requirements that dictate a certain layout, or behavior on those elements you discover that some things you can't do, others you can only do in certain way, maybe in some browsers. Latest example of this is native input type=date: I want to use it every time I am tasked with making something that has date input, not once did it offer flexibility to meet the requirements (you can't format date, I don't think there is a way to hide clear button on ff, no duration input, etc...). Next time I'm just not gonna bother and reimplement all of it myself.