Skip to content
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

[Save Form] ExampleImagery Save Form 'OK' button is made available before Form validation has completed #5184

Closed
2 of 6 tasks
unlikelyzero opened this issue May 10, 2022 · 4 comments

Comments

@unlikelyzero
Copy link
Collaborator

unlikelyzero commented May 10, 2022

Summary

We wrote a test for creating example imagery. When executing this test, we are detecting that console errors are thrown to the browser window.

When quickly creating an example imagery object, this error is thrown to console:

 [error] [Vue warn]: Error in nextTick: \"TypeError: Cannot read properties of undefined (reading 'scrollTop')\"

    found in

    ---> <MctTree> at src/ui/layout/mct-tree.vue
           <FormControlComponent> at src/api/forms/components/controls/Locator.vue
             <Root>,[error] TypeError: Cannot read properties of undefined (reading 'scrollTop')
        at VueComponent.isItemInView (webpack-internal:///./node_modules/vue-loader/lib/index.js??vue-loader-options!./src/ui/layout/mct-tree.vue?vue&type=script&lang=js&:488:53)
        at VueComponent.eval (webpack-internal:///./node_modules/vue-loader/lib/index.js??vue-loader-options!./src/ui/layout/mct-tree.vue?vue&type=script&lang=js&:476:31)
        at Array.eval (webpack-internal:///./node_modules/vue/dist/vue.js:1997:14)
        at flushCallbacks (webpack-internal:///./node_modules/vue/dist/vue.js:1923:16)"

Expected vs Current Behavior

No console errors

Steps to Reproduce

This is really only possible through automation.

  1. Create ExampleImagery object
  2. Click 'Ok' on Save form immediately as it appears
  3. Note the console error thrown

This is an e2e test artifact. To view it, you can run this locally with npx playwright show-trace <path_to_trace>/trace.zip
trace.zip

Or by uploading it to https://trace.playwright.dev/

Environment

System:

  • OS: macOS 11.6.5
  • CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  • Memory: 737.49 MB / 16.00 GB
  • Shell: 5.8 - /bin/zsh

Binaries:

  • Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
  • npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm

Browsers:

  • Chrome: 101.0.4951.54
  • Chrome Canary: 103.0.5054.0

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?

Additional Information

@unlikelyzero unlikelyzero changed the title [Tree] Console Error thrown on save of example Imagery in certain circumstances [Save Form] ExampleImagery Save Form 'OK' button is made available before Form validation has completed May 10, 2022
@unlikelyzero
Copy link
Collaborator Author

Note: this is possibly related to a known chrome bug https://bugs.chromium.org/p/chromium/issues/detail?id=1324419

@shefalijoshi
Copy link
Contributor

@unlikelyzero How do we test this?

@akhenry
Copy link
Contributor

akhenry commented Jul 1, 2022

Verified fixed.

Verification steps

  1. In chrome I throttled my network connection to "Slow 3G"
  2. Created a new Example Imagery object
  3. Verified that the OK button is not available until the locator has fully loaded and a folder has been selected.

@unlikelyzero
Copy link
Collaborator Author

@shefalijoshi we upgraded the playwright browser version and added chrome-beta to our test matrix

@unlikelyzero unlikelyzero added this to Needs triage in Build 6 Blockers via automation Jul 17, 2022
@unlikelyzero unlikelyzero added this to To triage in Improve Test Coverage via automation Jul 17, 2022
@unlikelyzero unlikelyzero added this to the Sprint:2.0.7 milestone Jul 17, 2022
@unlikelyzero unlikelyzero moved this from Needs triage to e2e Test Added in Build 6 Blockers Jul 17, 2022
@unlikelyzero unlikelyzero moved this from To triage to Integrated in Improve Test Coverage Jul 17, 2022
@unlikelyzero unlikelyzero removed this from the Sprint:2.0.7 milestone Jul 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flake Flaky Tests or CI Results severity:blocker type:bug
Projects
Build 6 Blockers
e2e Test Added
Development

No branches or pull requests

4 participants