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
[BUG] Today Firefox Nightly + your ext 3.6.0 and 3.8.0 = ERROR #1409
Comments
Please state the actual version of firefox nightly. |
I have the same issue. |
This is tracked by Mozilla as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1774425 |
I don't think a Bugzilla report is needed for this one - I believe the browser feature detection function we were using to detect if it was Firefox was deprecated recently and would be removed in the near future (thus v103) As the user agent is not reliable to determine the browser. I will need to figure out a function that only Firefox and Firefox Android would have but not in Chrome.
...or draft up a patch for it as early as tonight since the preliminary research has been done as noted below. |
Until Chrome and other browsers decides to implement |
Try the build in the PR (follow the bot instructions to request a build or build it yourself) to see if it works in Nightly again. I haven't tested this myself (as I don't have/use Nightly at this time). If this doesn't fixes it, I'll probably have a better idea once Firefox Beta/Developer Edition starts using 103. |
works for me now. |
kennethtran93, Create a test extension, please, so that im can try your solution. "Build in the PR" is completely incomprehensible. Can I just get a download link? If this platform does not allow - well, give a link to the file hosting Figured out, sort of like - Very convenient, just beauty, thanks, github |
kennethtran93 |
I am currently running |
Tested aswell, errors seem to be gone with the PR. |
To get the download link for the build, comment in the relevant PR with But I will try to get some form of static link going, with a caveat note that the link will expire on or after the 90 day date, if that makes it any easier. |
I've been trying to see if I can get the download links from that actions page into that Pull Request (PR), but seems to require a whole separate workflow process to execute after the current workflow (the one that generates the build) is completed, not during the existing workflow as I cannot fetch the artifact ids that are at the end of each download link during the current workflow. Other people have already requested something similar to GitHub already about being able to get/reference the freshly uploaded artifiacts/build metadata from the current workflow (not downloading them in another step) |
Hi, The issue is now also reproducible on Firefox Beta: 103.0b4 (64 bits) |
Thanks for the update. Anything Firefox 103+ is affected, with the fix in the linked PR. I'll bump the version soon. |
Firefox beta here. I've had the extension disabled for the last couple of weeks because it's basically broken. I couldn't make heads nor tails of your PR instruction. Looking forward to you updating. TIA |
I didn't think I made the PR instructions too hard...go into that PR, comment with |
I'll just do a version bump to 3.8.1 to resolve this. |
3.8.1 has been approved/validated and released on Firefox addons. |
Resolved. Thank you. |
Acknowledgements
Describe the bug
After today update Firefox Nightly error appears =
"Error!
Type error for parameter options (Unexpected property "origins") for browsingData.remove.
"
The error appears periodically - when the browser is launched, when the pages are opened.
I restored the old version, 3.6.0, the error still occurs.
If you turn off your expansion = error stops appearing.
Apparently, the developers of Firefox changed something again.
To Reproduce
Expected Behavior
no error
Screenshots
No response
System Info - Operating System (OS)
win 10 64
System Info - Browser Info
firefox nightly today update (everyday new)
System Info - CookieAutoDelete Version
3.8.0 and 3.6.0
Additional Context
Now it’s time to fix ext, and not before.
The text was updated successfully, but these errors were encountered: