-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
🐞 Waterfox Issue List Tracker #538
Comments
Scratched from the list. What about the rest? |
idk about all of the rest. The ones I reported are still unresolved, the resource URI leak is still unresolved, and I think most of the others are still unresolved too. Not sure about this one though -
Will comment in that issue. |
Thanks for this list - it's actually quite helpful. I've started going through all the issues and patching them. If you guys can do local builds as well to test I'm not breaking anything, that would be appreciated 😄. I've been doing them myself and they're fine, but that's not too great of a test range as there are so many different configurations out in the wild. |
@Peacock365 Should #534 be added to this list? |
Thanks for working on the regressions, @MrAlex94 #404 doesn't seem to be fixable without major code rewrites, I have noticed. Even the current Firefox at times still has this problem. #416 seems to be fixable via mozilla/gecko-dev@6b36043a0db3 #422 seems to be fixable via https://github.com/MoonchildProductions/Pale-Moon/commit/6d773b16968b50c848083382b03bd99727c08f41 |
I could probably add a few more – I occasionally review issues in chronological order, or least recently updated – but I'm wary of this issue becoming too long (for me) to absorb. YMMV |
Linux users: how are builds for you? (On FreeBSD-CURRENT, an attempt to build 56.1.0_18 fails at audio/alsa-lib 1.1.2_1. I |
Working well for me. |
Would it be possible to create commits for the two issues I pointed to above the first @grahamperrin comment? After all, the code that fixes these is already out there (I linked to it in both cases)... |
Here is the list of known fixes again (so that it does not get buried in the thread): #416 can be fixed via mozilla/gecko-dev@6b36043a0db3 (see also @jbeich comment in the issue) #422 can be fixed via https://github.com/MoonchildProductions/Pale-Moon/commit/6d773b16968b50c848083382b03bd99727c08f41 #350 can be fixed via https://bazaar.launchpad.net/%7Emozillateam/firefox/firefox.trusty/view/1200/debian/patches/unity-menubar.patch #414 can be fixed via:
#515 can be fixed via: devtools.webide.enabled - false |
#166 won't be fixed with just that patch. And regardless, just reverting one patch when a whole lot has changed in the Chromium IPC is such a terrible idea. I'm not sure at this stage if it's worth supporting Vista or lower, as Mozilla have made good performance and security updates due to removing legacy support for those platforms. #350 isn't going to be merged in. Isn't Unity effectively abandoned since the release of Ubuntu 18.04 LTS? |
Well, in this case I think you can close issue #166 ... I see your reasoning for this one. With #350 I wouldn't be so sure, as two older LTS versions are still supported and as all versions prior to Ubuntu 18.04 had unity. It's up to you, but I don't really see a reason here not to merge it. Let's not forget that Ubuntu 16.04 will receive updates until 2021, so it is well worth to patch the issue for that version alone. Anyway, I hope the rest is helpful regardless. |
I just noticed that @MrAlex94 mentioned additional bugs that he wanted to fix here: https://blog.waterfoxproject.org/waterfox-56.0-release-download (Under "What's due in Q1 2018?") Well, I have found a potential fix for the XML Buffer Overflow Crash (Bug 485941): Furthermore, @MrAlex94 mentioned Bug 895096 (inconsistent widths of border-collapsed table borders), for this one there are fixes as well:
A font settings issue was brought up here: |
👍 #121 (comment) drew attention to two more Mozilla bugs:
… no fixes, though (unless I'm missing something). |
You missed something. This deals with Bug 1241717:
Mr. Straver hinted... |
So I'm focusing on getting all the security patches done, then will revisit this after. |
#433 is fixed. EDIT: Fix reverted as insufficient. |
Could you maybe add a checklist to the issue description? That way it might be easier to track the status how many issues are already resolved. :) |
Should I begin adding other open issues? |
Sure, I did just set one up now. Feel free to do so. The two criterions I used to track "real" issues down are as follows:
I think those two criterions make sense. I am anticipating your further entries. |
Okay have updated the list and re-organised it a bit. Shame I can't take over issues so @Peacock365 doesn't get bombarded with notifications :-) |
expect a new current build soon? |
Couple things to consider adding to the list of Waterfox Current specific issues? -
I'm not able to create pull requests for these issues, since:
|
Hmm, I can seem to build with the current .mozconfig, maybe I've got a local change or ENV variable set. I will double check |
Curious, will there be a new Current build soon? Not being pushy just saw that Classic was updated but no Current build. |
This is issue has been closed and replaced with this issue, since GitHub does not allow changing ownership of issues. |
Hey there!
This is a list of Waterfox bugs yet unresolved. No guarantee for completeness. Should some of them be resolved by now, feel free to inform me. I will delete the corresponding entries in this case. This issue was created in an attempt to create an overview and as a potential starting point for sorting them out.
Waterfox General
Waterfox Classic
| POSSIBLE SOLUTION: https://bugzilla.mozilla.org/show_bug.cgi?id=1415921#c0
| POSSIBLE SOLUTION: https://github.com/MoonchildProductions/Pale-Moon/commit/6d773b16968b50c848083382b03bd99727c08f41
Mozilla has caught an Obj-C exception [NSInvalidArgumentException: -[NSImage drawInRect:]: unrecognized selector sent to instance 0x136655880]
Waterfox Current
Features to keep
Issues that are planning to be deprecated by Mozilla, but will be kept by Waterfox
ALREADY FIXED / NOT AN ISSUE ANYMORE:
The text was updated successfully, but these errors were encountered: