Extension stopped working #51
Comments
|
Not working for me either :( |
|
It also doesn’t work on my chrome |
|
Try changing the LeetCode UI to the old version until the issue gets fixed |
Do you mean to stop using the Dynamic layout and revert to split view mode? I tried this but still failed |
|
@hyunjinjeong I can fix this quickly, will you accept my pull request? |
|
When you click your profile icon, there is a I'm sorry but I'm not a maintainer 😢 |
Enhanced the function isLeetCodeV2 to more accurately determine if the current page is a version of LeetCode. The function now checks for the presence of specific root elements and body classes that indicate whether the page is using Chakra UI light or dark themes, as well as the presence of the "__next" root element. This ensures a more reliable and precise detection of LeetCode's version and UI themes, improving the overall functionality of the script. Issue: QasimWani#51
|
Hi @arunbhardwaj, I've submitted a pull request addressing the issue with the LeetCode V2 detection function. I've made enhancements to the These changes have been thoroughly tested on my local machine with different scenarios. The extension now performs more reliably with the updated logic. I look forward to your feedback and am happy to make any further adjustments as needed. Thank you for your time and consideration. |
|
Is it working now for other ? Still not working for me? |
It works in the pull request branch, no one has merged it so far |
|
Still not working 😢 |
|
Not working now. |
Update LeetCodeV2 detection mechanism; Rehandle submit by keyboard shortcuts; Use MutationObserver to determine when the submit button elements are loaded BREAKING CHANGE: 🧨 Detecting LeetCodeV2 by the presence of submit button ✅ Closes: QasimWani#51
|
Still not working |
|
not working brother |
|
I hope this PR is merged and deployed soon. |
|
New version is published to chrome store asking for new perms but there's no new commits to the repo? Uninstalling until things become clear |
|
update: while chrome did prompt me to allow new permissions on leethub (and I've had it installed for about 3 weeks), the chrome store page is showing it hasn't been updated since July 25, 2023. I'm not sure what prompted chrome to show that message, but some communication from the author would be appreciated. |
|
If @arunbhardwaj no longer has time for this project, I would suggest creating a new repository to continue the work. What do you guys think? But let's wait a few more days, maybe he's just temporarily busy :) |
|
I have forked this repository and will continue to work on the new project. It looks like the original maintainer doesn't have time at the moment. Please help to improve this awesome plugin. Your pull requests are welcome! Please check: https://github.com/raphaelheinz/LeetHub-3.0/ |
|
@raphaelheinz Did you upload leethub 3.0 to Chrome web store, or not yet? |
it probably takes a few days to get approved |
|
I have submitted the plugin to the Chrome web store. It still needs to get approved. Should be available soon. I will add the link to my repository as soon it is available. |
|
@raphaelheinz I created a new fix in this repository https://github.com/raphaelheinz/LeetHub-3.0 here raphaelheinz/LeetHub-3.0#1, because now extension does not work without sending correct submissionId field |
|
Great work @aystream! Thank you very much, I will update my submission |
|
Finally I am happy to announce that Google approved Leetcode-3.0. It is available in Chrome Web Store from now on. Please check this repository and don’t forget to star so that you stay updated: |
|
Not working for me even with old UI. Also, of possible, please implement for new UI. |
Look at here https://github.com/raphaelheinz/LeetHub-3.0 , https://chromewebstore.google.com/u/1/detail/leethub-v3/kdkgpjpenaeoodajljkflmlnkoihkmda |
|
The extension still isn't working for me either, since Nov 7, 2023 (so almost 2 months) :( |
* Fix detection of LeetCode V2 using improved document query logic Enhanced the function isLeetCodeV2 to more accurately determine if the current page is a version of LeetCode. The function now checks for the presence of specific root elements and body classes that indicate whether the page is using Chakra UI light or dark themes, as well as the presence of the "__next" root element. This ensures a more reliable and precise detection of LeetCode's version and UI themes, improving the overall functionality of the script. Issue: #51 * Fixed submissionId for send solve
The Chrome extension stopped working since about 22 hours ago. This happened before and the problem would be gone if I tried to submit on LeetCode a few more times. But this time the issue persists. I was wondering if there’s any bug or is there any solution for the issue on my end?
The text was updated successfully, but these errors were encountered: