-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'querySelectorAll') #124
Comments
Thanks @lookfirst, got this error too - looking into it! |
Thank you sir. I'd submit PR's but I honestly can't work in JS... I'm so used to TS... would you be open to a conversion? |
@lookfirst sure! I've been contemplating for I don't know how long to do a massive refactor and rewrite the extension in TS. Would LOVE help with that too. Till then if you have capacity to look into this error and try your hand at it, I'd love to help you out! 🙂 |
It looks like |
Thanks for the headsup @theY4Kman, I'll hopefully get time this weekend to deepdive into the issue, but the scope itself seems pretty large and would require a large-scale refactor... not looking forward. 😔 |
Try emailing @dang and asking him to add it back or make it simpler? I bet
he would be responsive.
…On Nov 18, 2022 at 2:05:46 AM, Mihir Chaturvedi ***@***.***> wrote:
Thanks for the headsup @theY4Kman <https://github.com/theY4Kman>, I'll
hopefully get time this weekend to deepdive into the issue, but the scope
itself seems pretty large and would require a large-scale refactor... not
looking forward. 😔
—
Reply to this email directly, view it on GitHub
<#124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAU224I37PSDX4HFL4NNYDWI5IHVANCNFSM6AAAAAAR7E2ZR4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Oddly, ran across this whole blog post on |
@plibither8 you forget me? ;-) |
I ran into the same issue. |
The way this extension is coded, it breaks everything. |
This still seems to be an issue. |
I'd guess, this thing is dead. |
The extension mostly works with my PR applied to it. #125 It does seem dead, which is ok. It really does need a full rewrite. I've been collecting notes on what a future version of this extension would look like, at some point, I'll find the time/motivation to start coding. |
The text was updated successfully, but these errors were encountered: