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
var renderedChildren = getRenderedChildren(getRenderedComponentVersion(reactComponent, getRootElsReact16()));
?
or well, could the children be looked at in the context of the component.alternate (?)
The getRenderedComponentVersion is already called when we look for the component corresponding to a certain dom node (which is where the search for children starts):
but we never look at the component.alternate during the search for nested children
Came across this when trying to access the children of a component that is wrapped by the react-i18next@7.8.3 translate(Component) wrapper, when doing some .findReact(A).findReact(B).findReact(C). In which case, one of the intermediate components has no child, but its alternate does have the child with which the search should continue.
The text was updated successfully, but these errors were encountered:
testcafe-react-selectors/src/react-16/index.js
Line 125 in 9e43d4b
could this line be something like
var renderedChildren = getRenderedChildren(getRenderedComponentVersion(reactComponent, getRootElsReact16()));
?
or well, could the children be looked at in the context of the component.alternate (?)
The getRenderedComponentVersion is already called when we look for the component corresponding to a certain dom node (which is where the search for children starts):
testcafe-react-selectors/src/react-16/react-utils.js
Line 106 in 9e43d4b
but we never look at the component.alternate during the search for nested children
Came across this when trying to access the children of a component that is wrapped by the react-i18next@7.8.3 translate(Component) wrapper, when doing some .findReact(A).findReact(B).findReact(C). In which case, one of the intermediate components has no child, but its alternate does have the child with which the search should continue.
The text was updated successfully, but these errors were encountered: