-
Notifications
You must be signed in to change notification settings - Fork 4
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
filingCookie is undefined…breaks extension #371
filingCookie is undefined…breaks extension #371
Comments
Thanks John. Any idea why this isn't breaking the extension for more people (I don't have any other reports?) |
Historically it has not broken it for me, so I'm sure it relates to the exact order of cookies that I have right now, and probably some other bug that relates to why I lack an So, this probably only affects filing users and probably only somewhat randomly. If it's helpful, here's the edited value of
But really, I think, just fix the missing guard and move on? |
Seems simple enough. Thanks, I'll put it on Eduardo's backlog once he finishes a couple other things that are high priority. |
The extension seems to be currently broken for me, probably specific to my cookie configuration.
But it's also clear the code is broken. I get this error:
which is from this code in pacer.js:
which fails to guard
filingCookie
before calling.match()
.Prior to freelawproject/recap-chrome@e2a07cf (Fri Nov 18 20:26:39 2022 -0400) this code properly guarded
filingCookie
beforematch()
.A similarly robust check should be applied here.
Not sure what the cookie pattern trigger is. I'll take my chocolate chips cooked on hot East Coat asphalt concrete with a few mirrors and maybe a lens, please.
The text was updated successfully, but these errors were encountered: