Re: Opinions wants: deprecate maction from MathML 4 (full) spec?

Hi Neil, all,

A successful <maction> would have probably needed a level of
specificity similar to HTML's <form>, and a similar level of adopter
interest...

I suspect using the available "class" and "data-*" attributes together with
JavaScript+CSS over MathML will encourage more mainstream web developers to
create MathML-based web apps. And deprecating <maction> clearly signals
that - so I'd be in favor.

The potential damage to accessibility can now also be mitigated with
strategic use of "intent" attributes.

Greetings,
Deyan


On Wed, Sep 4, 2024 at 4:09 PM Neil Soiffer <soiffer@alum.mit.edu> wrote:

> At our last meeting, we addressed issue 501
> <https://github.com/w3c/mathml/issues/501>: making actiontype optional
> matching core. We agreed to move forward on that.
>
> Note: maction in core is only supported to the extent that if grabs the
> first child and displays it.
>
> Actions have much more powerful alternatives via javascript in browsers.
> With no predefined actions, the question naturally becomes "what's the
> point of maction?". Because of this, the Math WG is soliciting opinions as
> to whether it should be deprecated in the MathML 4 Full Spec or should be
> kept.
>
> If you feel strongly about keeping or removing <maction> please reply with
> your rationale.
>
>