'region' Event member name seems awefuly generic

[RByers]

Canvas hit regions add a region member to MouseEvent and Touch. Is it me, or is the generic nature of this name likely to be confusing (eg. does it have to do with CSS regions?). Since nobody has (quite) shipped this API yet, perhaps we should consider making the name a bit more specific, eg. canvasHitRegion?

Not a big deal, I can live with region but wanted to raise the question before blink ships, just in case others feel similarly.

[domenic]

This seems like a good change to me. @smaug---- could maybe comment to get Gecko's position on changing their flagged implementation?

[annevk]

Also paging @junov @cabanier.

[smaug----]

As I said in #548 (comment) I think the whole .region should be removed.

[RByers]

Yeah it's a good question what value the region member adds. There's no mention of it in the original design notes. I suspect it's for cases where you want to do hit testing without also having fallback elements but perhaps that's not really a legitimate scenario?

You still need some identifier to pass to removeHitRegion and a string ID seems fine to me (nice not to have to necessarily track some return value identifier setTimeout style).

But we could certainly ship the rest of the feature without exposing region on the events, and see if there's demand for that piece. Like you say, as long as a DOM element is provided per region, then you already know what region was hit from the event.

[RByers]

@junov something else to ask Frank perhaps?