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
We notice that snapshots do not work well with (our) angular application(s). HIghlighting does not work and pinning often renders an empty page.
I included a video to show this. On initial rendering, you'll see two lists of questions. The first list has been rendered by angular components, the second list is straight html that we have put directly in index.html. For both lists we assert the question descriptions. Assertion works well for both lists, but the snapshot feature fails on the list that has been generated by angular.
You'll see that snapshot pinning and highlighting works well for for the second list (Straight html), but not for the first list (controlled by [Angular). Screencast from 08-08-24 11:50:46.webm
Is this common behaviour for Angular applications, or should this be caused by the specific way our angular components work?
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
-
We notice that snapshots do not work well with (our) angular application(s). HIghlighting does not work and pinning often renders an empty page.
I included a video to show this. On initial rendering, you'll see two lists of questions. The first list has been rendered by angular components, the second list is straight html that we have put directly in index.html. For both lists we assert the question descriptions. Assertion works well for both lists, but the snapshot feature fails on the list that has been generated by angular.
You'll see that snapshot pinning and highlighting works well for for the second list (Straight html), but not for the first list (controlled by [Angular).
Screencast from 08-08-24 11:50:46.webm
Is this common behaviour for Angular applications, or should this be caused by the specific way our angular components work?
Beta Was this translation helpful? Give feedback.
All reactions