Another way to get web dev input: one-click intent button on MDN pages

Just recording this idea I had while looking at sign()'s MDN page:

In addition to existing large-scale web development surveys (State of …) and MDN short surveys, I wonder if a good way to get signal could be a simple button in Limited or No availability features callout that authors can press to indicate they wanted to use this feature, but couldn't due to browser support.

I'd argue this provides better data than surveys, since it's contextual, just-in-time, rather than requiring people to look back and remember, which is prone to recency bias.

Sure, it's prone to abuse, but presumably there are mitigations in place for short surveys as well.

It could even be framed around "Notify me" [when it reaches full support] so that there's an immediate benefit, or just a more vague "Interested" (similar to sentiment chips) then asks if they want to be notified.

Sure, there's a confound that some features are visited more than others but is that really a confound? Presumably popularity is also a prioritization factor. But also, one could compare the number of interest clicks to the general page visits and use the ratio instead of the raw number to control for that.

Including something similar on caniuse could also provide useful signal.

cc @atopal @foolip

The issue names no repository files, tests, or implementation entry points. Start by reviewing the sign() MDN page, the existing MDN short-survey flow, and the caniuse comparison mentioned; done would require an agreed design and scope for contextual interest or notification input.