You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app auto-upgraded to 3.4.0 from 3.3.1 and broke with this error:
saved.shift is not a function
I'll append the browser version in a comment shortly.
Reacted by Aziz Gazanchiian, Alexander Shartdinov, crmouli, cr-nz, Aldo Valverde, Ingo Hinterding, Justin Mayfield, Zoup, Dima Krutolianov, Sergey Margaritov and 3 more
user_agent: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36"
trace: "TypeError: saved.shift is not a function
at HTMLDivElement.handler (...)
at HTMLDivElement.dispatch (...)
at HTMLDivElement.elemData.handle (...)
Sorry, there is not enough information to go on here. You can find help on https://stackoverflow.com. If after sorting out the issue you find there is a change needed in jQuery core, please open a new issue and follow the instructions in the issue template, including providing a test case from https://jsbin.com.
@dsandber Unfortunately, we cannot do much without a test case we can run, the error itself doesn't say much. We usually require a small test case without external dependencies as most errors user have is actually a bug on their app part but since this code is new in 3.4.0 & it's one of the most trickiest new part, it's possible we broke something so I'd be open to looking at a slightly bigger test case. But I still need at least a website with this bug, with an easy way to reproduce it myself. Ideally I'd have both one with jQuery 3.3.1 & 3.4.0 to compare but I could try with just 3.4.0 as well if the older one is not available.
Yeah, I understand -- probably best to wait until more people report this error and hopefully someone can develop a simple test case. I literally wouldn't know where to start since the stack trace doesn't include my code, the error doesn't happen consistently, and I don't understand what the code I quoted does.
Given three independent reports, perhaps the bug should be re-opened to make it easier for others to find? (since closed bugs aren't searched by default)
GitHub currently pushes recommendations to all repos using jquery <3.4.0 to upgrade due to CVE-2019-5428. I saw that, so I checked out the release blog post which currently says:
There should be no compatibility issues if upgrading from jQuery 3.0+.
So after some brief sanity testing (which seemed fine) I deployed and then errors started arriving.
Given this bug, I recommend you change the wording on the blog post for 3.4.0.
Reacted by Ben Moroze, Roman Usherenko, Tyler Golias, Slawa and Alexey Ratnikov
Activity
dsandber commentedon Apr 11, 2019
user_agent: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36"
trace: "TypeError: saved.shift is not a function
at HTMLDivElement.handler (...)
at HTMLDivElement.dispatch (...)
at HTMLDivElement.elemData.handle (...)
timmywil commentedon Apr 11, 2019
Sorry, there is not enough information to go on here. You can find help on https://stackoverflow.com. If after sorting out the issue you find there is a change needed in jQuery core, please open a new issue and follow the instructions in the issue template, including providing a test case from https://jsbin.com.
dsandber commentedon Apr 11, 2019
Sorry, because it wasn't triggered directly by my code, and because it doesn't seem to happen consistently, I don't know how to create a test case.
timmywil commentedon Apr 11, 2019
Fair enough, but the issue needs to be fleshed out more regardless.
dsandber commentedon Apr 11, 2019
Luckily "saved.shift" only occurs once in the source-code. Strange that the comment says IE <= 9 - 11+ but that it is being run on Chrome.
Seems to happen because saved is not an array, example:
mgol commentedon Apr 12, 2019
@dsandber Unfortunately, we cannot do much without a test case we can run, the error itself doesn't say much. We usually require a small test case without external dependencies as most errors user have is actually a bug on their app part but since this code is new in 3.4.0 & it's one of the most trickiest new part, it's possible we broke something so I'd be open to looking at a slightly bigger test case. But I still need at least a website with this bug, with an easy way to reproduce it myself. Ideally I'd have both one with jQuery 3.3.1 & 3.4.0 to compare but I could try with just 3.4.0 as well if the older one is not available.
dsandber commentedon Apr 12, 2019
Yeah, I understand -- probably best to wait until more people report this error and hopefully someone can develop a simple test case. I literally wouldn't know where to start since the stack trace doesn't include my code, the error doesn't happen consistently, and I don't understand what the code I quoted does.
fancyapps commentedon Apr 12, 2019
I noticed this error message after upgrading to 3.4.0., too. I could not figure out when/why, I`ll try to create a minimal example.
XhmikosR commentedon Apr 13, 2019
@mgol we hit this in Bootstrap 4.x https://travis-ci.org/twbs/bootstrap/jobs/519620443
Going back to 3.3.1 our tests pass.
dsandber commentedon Apr 13, 2019
Given three independent reports, perhaps the bug should be re-opened to make it easier for others to find? (since closed bugs aren't searched by default)
dmethvin commentedon Apr 13, 2019
Reopening it is fine, but we still don't have a test case. Can we at least get a stack trace?
XhmikosR commentedon Apr 13, 2019
The stacktrace is shown in the Travis build, but it's using the minified build. AFAICT it only affects IE 10/11, at least in our test suite.
dsandber commentedon Apr 13, 2019
My second comment includes a stack trace.
Chrome too.
16 remaining items
ewolfman commentedon Apr 17, 2019
Hi,
When is the 3.4.1 release date?
timmywil commentedon Apr 17, 2019
There's no set date, but it will probably be next week or the week after.
Downgraded jquery
Downgraded jquery
dmnd commentedon Apr 25, 2019
I just broke production because of this bug.
GitHub currently pushes recommendations to all repos using jquery <3.4.0 to upgrade due to CVE-2019-5428. I saw that, so I checked out the release blog post which currently says:
So after some brief sanity testing (which seemed fine) I deployed and then errors started arriving.
Given this bug, I recommend you change the wording on the blog post for 3.4.0.
Event: Fix handling of multiple async focus events
mgol commentedon Apr 29, 2019
Fixed by PR #4354 (commit 24d71ac).
vincentwoo commentedon May 1, 2019
Any word on when a 3.4.1 release will be cut?
jcubic commentedon May 1, 2019
@vincentwoo I'm also interested when it will be out, It seems that only iOS 10 test are waiting https://github.com/jquery/jquery/milestone/20
timmywil commentedon May 1, 2019
jQuery 3.4.1 has been released! https://blog.jquery.com/2019/05/01/jquery-3-4-1-triggering-focus-events-in-ie-and-finding-root-elements-in-ios-10/
LPS-101410 Update jQuery to avoid focus/blur error jquery/jquery#4350
LPS-101410 Update jQuery to avoid focus/blur error jquery/jquery#4350
Event: Fix handling of multiple async focus events