Decide what to do about the data for the dragexit event (drop completely? maintain the data indefinitely?) and ondragexit event handler

[sideshowbarker]

See discussion in #6710

Unless we have evidence that developers are actually relying on dragexit and ondragexit (despite them apparently only having been implemented in Gecko, and not in any other engines), I would think that developers aren’t going miss them being gone from BCD, if were to drop them.

The alternative is to keep entries for them in BCD. But if we do that, it’s not clear to me at least what the plan is for retaining them. We keep them in BCD forever?

[ddbeck]

I agree that it's unlikely that developers are going to miss them if we drop the data. However, I do think BCD's posture to date has been to record things as they exist, even if they're not advisable to use. This is somewhat reflected in the guideline for irrelevant features, which suggests dropping data only when it stops shipping in any browser.

The alternative is to keep entries for them in BCD. But if we do that, it’s not clear to me at least what the plan is for retaining them. We keep them in BCD forever?

Ideally, Gecko drops the feature someday, which starts the clock on removing it from BCD under the irrelevance guideline. Bug 1635018 proposes removing it. I'm partly inclined to comment there that tracking this feature is a drag (pun intended) on BCD. But if it's never removed from the engine and Firefox keeps shipping it, then I suppose it stays in BCD indefinitely.

All that said, if you still think it's a good idea to drop this data while it's still in an actively developer browser, then I'd like to hear your ideas for a guideline that would allow for it gracefully.

[sideshowbarker]

… BCD's posture to date has been to record things as they exist, even if they're not advisable to use. This is somewhat reflected in the guideline for irrelevant features, which suggests dropping data only when it stops shipping in any browser.
…
Ideally, Gecko drops the feature someday, which starts the clock on removing it from BCD under the irrelevance guideline. Bug 1635018 proposes removing it.

OK, that’s all clear to me now. I honestly had just not be aware yet of what the existing guidelines has to say for this.

All that said, if you still think it's a good idea to drop this data while it's still in an actively developer browser, then I'd like to hear your ideas for a guideline that would allow for it gracefully.

Nope — in light of what the existing guidelines have to say, I agree we need to keep it for now, so I retract my suggestion about dropping it.

So I’m gonna go ahead and close this. But if there’s actually more that needs to be resolved here, then of course feel free to reopen it.