Hmm, maybe this is a recent accidental regression for Figma plugins in the browser?
Wonder if this is related to an issue we are likewise facing where Figma.on(“drop”) events are not firing as expected for us in the browser despite working just fine in the Figma desktop app.