Thank you very much for the reply. I’m sure you are correct that the component works on the latest tests-passed version, but I prefer to stick to the beta releases when possible. My post was partly meant to be a warning to anyone else who sticks to the betas like me, and partly a hint to the team that perhaps the API version requirement for this component is more strict than it needs to be.
I think it’s a bug because the .discourse-compatibility file specifically lists revision 1398eeeff550c1da186a47b6d3878d3230f62340 as working with 3.2.0.beta2, and I don’t think there’s any way it can.