-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: recentered form view #591
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -992,7 +992,8 @@ describe('FormEditor', function() { | |
}); | ||
|
||
|
||
it('should move row', async function() { | ||
// flaky, skipped for now until we migrate it to playwright | ||
it.skip('should move row', async function() { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This becomes laggy due to the absolute positioning now, I think. That's always hard to test, so I got your rationale about this particular test. In general, I think the dragging tests make sense, as the behavior is predictable. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we at least add an comment above the test why we skip it and maybe a note that we could solve it with proper integration testing? Or should we remove it entirely? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can try to move this test o Playwright when I create the setup |
||
|
||
// given | ||
formEditor = await createFormEditor({ | ||
|
@@ -1022,6 +1023,7 @@ describe('FormEditor', function() { | |
clientX: bounds.x, | ||
clientY: bounds.y | ||
}); | ||
|
||
endDragging(container); | ||
|
||
// then | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe we have to keep
flex: unset
, otherwise it will mess up the height of the previews.