Invokers (invoketarget & invokeaction)

[keithamus]

Request for Mozilla Position on an Emerging Web Specification

• Specification title: Invokers
• Specification or proposal URL (if available): Add invokers (invoketarget & invokeaction) whatwg/html#9841
• Explainer URL (if available): https://open-ui.org/components/invokers.explainer/
• Proposal author(s) (@-mention GitHub accounts): @keithamus
• Caniuse.com URL (optional): N/A
• Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1856430
• Mozillians who can provide input (optional): @smaug----, @zcorpan, @emilio

Other information

This is a request for position just on the invoketarget and invokeaction parts of the Invokers explainer (excluding interesttarget and interestaction).

[keithamus]

I2P Chrome and is in Chrome Canary behind the Experimental Web Platform Features flag.

[smaug----]

I think we're positive on prototyping this. There might be still some things to sort out before the feature is ready
(see the feedback to the intent-to-prototype email, which is very similar to what was discussed at TPAC too), but overall this is looking reasonable approach.
And hopefully after this we could get rid of the weird popover specific attributes.

[lukewarlow]

Just as an fyi OpenUl have agreed (openui/open-ui#952 (comment)) to an initial scope for invokers of just popover and dialog actions, along with custom actions.

Hopefully this helps with some concerns regarding security of some of the additional proposed actions.

[smaug----]

That may make things possibly more complicated, since the same security setup should apply to all invokers. So we likely will need to solve the generic issues before the feature can ship.

[mfreed7]

Quick ping here, just to make sure Mozilla would still be supportive if the attribute names get renamed:

whatwg/html#9625 (comment)