-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Error: Cannot read property 'style' of null #22533
Comments
go/ampe/COuC3YCVi7zk7wE |
Looks like there was a spike on Sunday in the error rate, but has been lower before/after. I can't reproduce this when loading the canary version. I'm not 100% sure what is going on here. Here are something I know: The error is happening here, with
This is set on the first touch (from touchstart) here:
via:
At that point, I refactored this logic, but the data flow should be the same. The one thing I did change was I made the function use an object parameter instead of simple arguments, but I can't imagine that has any effect. The minified code looks something like: a.Na.startSwipe({
swipeElement: a.I,
hiddenElement: c || b,
mask: a.aa,
overlay: a.T
}) and U.prototype.startSwipe = function(a) {
var b = this
, c = a.swipeElement
, d = a.hiddenElement
, e = a.mask
, f = a.overlay;
this.oa = c;
this.Ba = d;
this.aa = e;
this.ja = f;
this.Ea(function() {
Ab(b)
})
} It is a little odd that the object properties are not being renamed, but it seems to be fine. |
Reopening until we can confirm whether or not we fixed this. |
This is still not fixed, and it's by far the biggest error report in production. |
I think we're receving badly ordered gestures, which is causing ampproject#22533. Now, if we receive a subsequent gesture without first receving the `first` geture, we'll early exit. That should solve the bug. I'm also adding error reporting, so we can track down exactly how this is happening.
I think we're receving badly ordered gestures, which is causing #22533. Now, if we receive a subsequent gesture without first receving the `first` geture, we'll early exit. That should solve the bug. I'm also adding error reporting, so we can track down exactly how this is happening.
As of writing, both this error and the attempted fix ("subsequent without first" error in #25375) are both present and firing at high volume in RTV 1911191835190. The latter is about half the volume of the first. |
I think we're receving badly ordered gestures, which is causing ampproject#22533. Now, if we receive a subsequent gesture without first receving the `first` geture, we'll early exit. That should solve the bug. I'm also adding error reporting, so we can track down exactly how this is happening.
@ampproject/wg-ui-and-a11y Can you please reassign this issue? Seeing 8k occurrences in the current canary |
Assigning @wassgha to take a look. |
About 12k errors in new canary on stackdriver. Sample stack trace:
Looks to be
amp-lightbox-gallery
related.cc/ @ampproject/wg-ui-and-a11y
The text was updated successfully, but these errors were encountered: