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
{{ message }}
Repository navigation
Unable to match from a form submitted response into root layer
#777
Uncaught (in promise) up.CannotMatch: Could not find common target in current page and response (tried selectors [#row-103, .content] in layer "root")
I put the .content into the up-fallback to inspect the HTML from root. If I don't use it, it does not throw the error, but replaces the body with the tr content (without the tr tag itself).
Because I could not overcome this, I created a very simple project to debug the issue.
In this simple project (with super simple HTML) it works as intended. In this simpler project I did not use up-match. It just worked.
I also tried to put some breakpoints into unpoly's code to understand why it's not being able to match and swap the tr elements, but I was unable to come to a conclusion, because when I use up-match first, I can debug to a point where it matches it in response and in document, but it keeps trying to match and I could not get the point when it does not match anymore.
I just found #91 and I could resolve my issue with it.
I think that updating table rows might be a pretty common case. How about including this common case in the docs?
Are you open to receive a PR regarding this?
I just found #91 and I could resolve my issue with it.
I think that updating table rows might be a pretty common case. How about including this common case in the docs?
Are you open to receive a PR regarding this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
I just found #91 and I could resolve my issue with it.
I think that updating table rows might be a pretty common case. How about including this common case in the docs?
Are you open to receive a PR regarding this?