[
https://issues.apache.org/jira/browse/WICKET-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066111#comment-18066111
]
ASF GitHub Bot commented on WICKET-7177:
----------------------------------------
kbachl commented on PR #1385:
URL: https://github.com/apache/wicket/pull/1385#issuecomment-4068221279
So if I understand it correctly, the whole idea behind this patch is to
allow to overcome a limitation jQuery has?
Wouldn't it be more logical to rethink the jQuery need itself?
When looking at the code the only thing I've noticed is the absence of a
default legacy method to be used when no replacementMethod is available? - this
might be a problem for anyone that did some manual JS to talk to wicket before,
wouldn't it be?
> Allow alternative replacement methods to support Ajax for SVG and MathML
> ------------------------------------------------------------------------
>
> Key: WICKET-7177
> URL: https://issues.apache.org/jira/browse/WICKET-7177
> Project: Wicket
> Issue Type: Improvement
> Reporter: Johan Stuyts
> Priority: Major
> Labels: ajax, mathml, svg, websocket, xml
>
> jQuery is used to replace markup in Ajax (and WebSocket) requests. But jQuery
> does not support replacing XML, so dynamically updating (a part of) an
> embedded SVG or MathML formula is not possible.
> This will add the possibility to use alternative replacement methods for
> partial markup replacement. Using an alternative replacement method consists
> of 2 steps:
> * Register the replacement method in the user agent.
> * In partial page updates specify with which replacement method the markup
> of a component must be replaced.
> The user is in full control: which replacement method to use can be specified
> per component.
> Initially only a replacement method for XML is provided. This can be used to
> update (parts of) SVGs and MathML formulas. Note that full compatibility and
> feature parity with the standard jQuery replacement method is not a goal. It
> is also not a full-blown SVG or MathML library, but is required to be able to
> build one.
> The changes are fully backward compatible with existing Wicket code. There is
> a tiny runtime impact on both the server and client side, as checks for the
> presence of replacement method properties/attributes must be made.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
