volosied commented on PR #736:
URL: https://github.com/apache/myfaces/pull/736#issuecomment-2316639835
This fix is only to queue the action event for some scenarios.
When 4606 was introduced, it allowed all ajax calls (on the form's submit
button) to invoke the action event. For example:
```
<div>
<h:inputText />
<h:commandButton id="confirm3" value="listner3"
action="#{ajaxEventBean.confirm()}" >
<f:ajax event="mouseover"/>
</h:commandButton>
</div>
```
The mouseover event would trigger a form submission. I don't think that's
intended. It didn't happen prior to 4606.
I don't think the current 4606 behavior is correct here, so maybe we should
revert it. However, the question I have is which ajax events should trigger an
action event? I'm having a hard time find what the spec says here.
Current options:
1) Revert 4606
2) Only allow certain ajax events to trigger action events.
3) Other
Although..... re-looking at the fix, the `isSubmitted` method does handle
ajax via the `HtmlRendererUtils.isPartialOrBehaviorSubmit(facesContext,
clientId);` check in the return.
Perhaps some other refactoring could be done here...? Let me push up a new
commit.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
