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

Quick search fires error #14274

Closed
jonathanKingston opened this issue Mar 22, 2018 · 5 comments
Closed

Quick search fires error #14274

jonathanKingston opened this issue Mar 22, 2018 · 5 comments

Comments

@jonathanKingston
Copy link
Contributor

@jonathanKingston jonathanKingston commented Mar 22, 2018

Preconditions

  1. Magento 2.3-develop branch

Steps to reproduce

  1. Type a term into the quick Ajax search field (#search) that doesn't exist in the database
  2. Press Home keyboard key

Expected result

  1. No error

Actual result

  1. TypeError: this._getFirstVisibleElement(...).addClass is not a function
@magento-engcom-team
Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Mar 23, 2018

@jonathanKingston, thank you for your report.
We've acknowledged the issue and added to our backlog.

@drashmk
Copy link
Contributor

@drashmk drashmk commented Mar 24, 2018

I’m working on it #distributed-cd

@magento-engcom-team
Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Mar 24, 2018

@drashmk thank you for joining. Please accept team invitation here and self-assign the issue.

@drashmk drashmk self-assigned this Mar 24, 2018
drashmk added a commit to drashmk/magento2 that referenced this issue Mar 24, 2018
…ch term does not exist on pressing Home or End button magento#14274
drashmk added a commit to drashmk/magento2 that referenced this issue Mar 24, 2018
@magento-engcom-team
Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Mar 26, 2018

Hi @jonathanKingston. Thank you for your report.
The issue has been fixed in #14301 by @drashmk in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

@magento-engcom-team
Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Apr 26, 2018

Hi @jonathanKingston. Thank you for your report.
The issue has been fixed in #14839 by @julienanquetil in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.5 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants