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

Close prompt immediately after click ok instead of wait ajax request #28739

Merged
merged 1 commit into from
Jun 24, 2020

Conversation

Nazar65
Copy link
Member

@Nazar65 Nazar65 commented Jun 16, 2020

Description (*)

The prompt need to be closed after press ok button instead of wait ajax request, because after unsuccessful response there is conflict with alert prompt

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Alert appears twice when the folder creation is not successful adobe-stock-integration#840

Manual testing scenarios (*)

  1. On CMS edit page open media gallery
  2. Load 5 images from Adobe Stock. One by one without page reload.
    Every next save of the image will drastically decrease performance. (Memory leak suspected)
  3. Click "Create Folder"
  4. Type in "Folder"
  5. Click "OK"
  6. When alert with a message "Please rename the folder Please rename the folder using only letters, numbers, underscores and dashes." appears, click "OK"
  7. Click anywhere on the dark overlay

Expected result (*)

  1. Alert appears only once

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Jun 16, 2020

Hi @Nazar65. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

@Nazar65
Copy link
Member Author

Nazar65 commented Jun 16, 2020

@magento run all tests

@Nazar65
Copy link
Member Author

Nazar65 commented Jun 16, 2020

Already covered by mftf test app/code/Magento/Cms/Test/Mftf/Test/AdminCheckCreateFolderEscapeAndEnterHandlesForWYSIWYGBlockTest.xml

@rogyar rogyar self-assigned this Jun 16, 2020
@rogyar rogyar added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Jun 16, 2020
@ghost ghost moved this from Pending Review to Ready for Testing in Pull Requests Dashboard Jun 16, 2020
@magento-engcom-team
Copy link
Contributor

Hi @rogyar, thank you for the review.
ENGCOM-7690 has been created to process this Pull Request

@VladimirZaets VladimirZaets added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jun 16, 2020
@engcom-Bravo engcom-Bravo self-assigned this Jun 17, 2020
@engcom-Bravo engcom-Bravo moved this from Ready for Testing to Testing in Progress in Pull Requests Dashboard Jun 17, 2020
@engcom-Bravo
Copy link
Contributor

engcom-Bravo commented Jun 17, 2020

✔️ QA Passed

Manual testing scenarios (*)

  1. On CMS edit page open media gallery
  2. Load 5 images from Adobe Stock. One by one without page reload.
    Every next save of the image will drastically decrease performance. (Memory leak suspected)
  3. Click "Create Folder"
  4. Type in "Folder"
  5. Click "OK"
  6. When alert with a message "Please rename the folder Please rename the folder using only letters, numbers, underscores and dashes." appears, click "OK"
  7. Click anywhere on the dark overlay

Expected result (*)

  1. Alert appears only once. After clicking OK the Attention message is closed immediately

@engcom-Bravo engcom-Bravo moved this from Testing in Progress to Extended Testing (optional) in Pull Requests Dashboard Jun 17, 2020
@engcom-Echo engcom-Echo self-assigned this Jun 17, 2020
@engcom-Echo engcom-Echo added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jun 17, 2020
@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Jun 17, 2020
@engcom-Echo engcom-Echo moved this from Extended Testing (optional) to Merge in Progress in Pull Requests Dashboard Jun 17, 2020
@lenaorobei lenaorobei added Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. and removed Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jun 22, 2020
@lenaorobei lenaorobei added this to the 2.4.1 milestone Jun 22, 2020
@magento-engcom-team magento-engcom-team merged commit ebd2c31 into magento:2.4-develop Jun 24, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jun 24, 2020

Hi @Nazar65, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@ghost ghost moved this from Merge in Progress to Recently Merged in Pull Requests Dashboard Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Lib/Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”.
Projects
Pull Requests Dashboard
  
Recently Merged
Development

Successfully merging this pull request may close these issues.

Alert appears twice when the folder creation is not successful
8 participants