I wouldn’t do that if I were you, as seems to cause more problems than it solves. Even if all browsers would render these elements, how can you guarantee that the end result would be the same on every browser?
Maybe one browser does makes them
inline, maybe another handles them as
block. Maybe a future release will create an element named
panel that behaves differently.
I’ve actually had a similar issue happen to me, where I create an
input[type="date"] element to make it’s purpose clear, and when the browsers started supporting with their own datepicker my datepickers broke horribly.
And now I wonder how hard it would be to add a middleware in Blaze that replaces