You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Marko 3 (and therefore the legacy compat layer in Marko 4) a template without a w-bind could define w-id and be included in a widget that could then getEl that id. Similarly, a template without a w-bind could specify a w-on event handler that points to function in a widget bound in another template that includes the current one.
Expected Behavior
This behavior should continue to work in the legacy compat layer.
Actual Behavior
It no longer works.
Possible Fix
The legacy layer has a getWidgetFromOut helper that used to be triggered by w- attributes in a template without a w-bind. Because these attributes now get transformed to their modern equivalent in the migration stage, this heuristic is no longer there to trigger the behavior. Some possible fixes:
Leave something in place to trigger this behavior
Embed the included template where it is used
Emit events and listen for events where the template is included & use getComponent().getEl() from the parent component
The text was updated successfully, but these errors were encountered:
Marko Version: 4.14.14
Details
In Marko 3 (and therefore the legacy compat layer in Marko 4) a template without a
w-bind
could definew-id
and be included in a widget that could thengetEl
that id. Similarly, a template without aw-bind
could specify aw-on
event handler that points to function in a widget bound in another template that includes the current one.Expected Behavior
This behavior should continue to work in the legacy compat layer.
Actual Behavior
It no longer works.
Possible Fix
The legacy layer has a
getWidgetFromOut
helper that used to be triggered byw-
attributes in a template without aw-bind
. Because these attributes now get transformed to their modern equivalent in the migration stage, this heuristic is no longer there to trigger the behavior. Some possible fixes:getComponent().getEl()
from the parent componentThe text was updated successfully, but these errors were encountered: