Skip to content

Initialize toolbar.js once #28838

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

Conversation

ptylek
Copy link
Contributor

@ptylek ptylek commented Jun 22, 2020

Description (*)

Continue work that was done by @Nagamaiah007 in #26097.
I changed approach to set events with proper scope of toolbar that javascript is initialized with in order not to process events twice. Previously _bind function was adding events for data-role selectors that were not assigned to this.element scope, so if we had two toolbars on the page (toolbar top and bottom), all events were incorrectly assigned with first toolbar initialization. This change fixes scope for these data-role selectors and won't trigger specific functions to be run twice.

Related Pull Requests

#26097: Update toolbar.js #25934

Fixed Issues (if relevant)

  1. Fixes chrome initiate two times toolbar.js #25934

Manual testing scenarios (*)

  1. Got to product list, search or advance search page
  2. Open developer tools -> Network tab (Chrome browser)
  3. Select/click any of the toolbar option like Grid/List, Sort By, or show X per page
  4. Network(Chrome Browser) selected/clicked link triggering two time and because of two time trigger backed doing twice process after canceled one also. (for verify put any log in to catalog->product->list controller).

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 22, 2020

Hi @ptylek. 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.

@ghost ghost 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 22, 2020
@ptylek
Copy link
Contributor Author

ptylek commented Jun 23, 2020

@magento run all tests

@ptylek
Copy link
Contributor Author

ptylek commented Jul 2, 2020

@magento run all tests

@ptylek
Copy link
Contributor Author

ptylek commented Jul 7, 2020

@magento run all tests

@ptylek
Copy link
Contributor Author

ptylek commented Jul 7, 2020

@magento run all tests

@ghost ghost assigned krzksz Jul 15, 2020
@krzksz krzksz added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests and removed Progress: ready for testing labels Jul 15, 2020
@magento-engcom-team
Copy link
Contributor

Hi @krzksz, thank you for the review.
ENGCOM-7834 has been created to process this Pull Request
✳️ @krzksz, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@engcom-Alfa engcom-Alfa self-assigned this Jul 15, 2020
@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Manual testing scenario:

  1. Got to the product list, search or advance search page;
  2. Open developer tools -> Network tab (Chrome browser);
  3. Select/click any of the toolbar options like Grid/List, Sort By, or show X per page;
  4. Network(Chrome Browser) selected/clicked link triggering two time and because of two time trigger backed doing twice process after canceled one also. (for verify put any log in to catalog->product->list controller).

Before: ✖️ On click/change link trigger two times

2020-07-15_12-40

After: ✔️ Link triggered once

2020-07-15_12-44

Toolbar functionality is still working as previously (expected).

@engcom-Echo engcom-Echo self-assigned this Jul 15, 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 Jul 15, 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 Jul 16, 2020
@magento-engcom-team magento-engcom-team merged commit 17f26a7 into magento:2.4-develop Jul 18, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 18, 2020

Hi @ptylek, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Catalog Partner: creativestyle partners-contribution Pull Request is created by Magento Partner 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: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

chrome initiate two times toolbar.js
5 participants