That is something we’ve definitely thought about and desired in the past, I was not aware that we could extend and whitelist the existing suite of allowed html. We do have a workaround for the issue already but it’s a regex that runs clientside to fix any remaining tag issues.
Any documentation or examples you could point us at?