Skip to content
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

Closed
15 of 51 tasks
Peacock365 opened this issue Apr 25, 2018 · 46 comments
Closed
15 of 51 tasks

🐞 Waterfox Issue List Tracker #538

Peacock365 opened this issue Apr 25, 2018 · 46 comments
Assignees

Comments

@Peacock365
Copy link

Peacock365 commented Apr 25, 2018

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

Waterfox Current

  • Separate out australis theme
  • Fix loading of all NPAPI plugins

Features to keep

Issues that are planning to be deprecated by Mozilla, but will be kept by Waterfox

ALREADY FIXED / NOT AN ISSUE ANYMORE:

@laniakea64
Copy link

Don't expose navigator.AddonManager to content
-> #204

#449

@Peacock365
Copy link
Author

@laniakea64

#449

Scratched from the list. What about the rest?

@laniakea64
Copy link

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 -

Ubuntu 17.04 mozconfig redirection error
-> #227

Will comment in that issue.

@MrAlex94
Copy link
Collaborator

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.

@laniakea64
Copy link

@Peacock365 Should #534 be added to this list?

@MrAlex94 MrAlex94 self-assigned this May 1, 2018
@Peacock365
Copy link
Author

Peacock365 commented May 1, 2018

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

@laniakea64
Copy link

URGENT!!!!!!! Resource leak
-> #235

Seems fixed in self build from d5c2541 👍

Zoom-in/Zoom-out mouse cursors don't display
-> #347

Fixed by d5c2541

@Peacock365
Copy link
Author

Peacock365 commented May 1, 2018

@laniakea64

I updated the list to reflect the fixes for #235 and #347 Thanks for the update.

#464 and #282 and #482 seem fixed, too.

@grahamperrin
Copy link

Adobe Flash Player 28.0.0.126 can not present its context menu, crashes, with Waterfox 56.0.1 on Linux · Issue #335 …

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

@grahamperrin
Copy link

grahamperrin commented May 2, 2018

… local builds as well to test I'm not breaking anything, …

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 can probably might work around it reasonably easily (https://redd.it/8gk2v3), I don't know whether things will be as easy in Linux environments.)

@laniakea64
Copy link

Linux users: how are builds for you?

Working well for me.

@Peacock365
Copy link
Author

Peacock365 commented May 6, 2018

@laniakea64

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)...

@laniakea64
Copy link

I don't have time to do more pull requests atm and I'm likely not the right person to do those anyway. #166 is Windows-specific and I only have Linux; I can't reproduce #416; and I don't understand the code related to #422 well enough.

@Peacock365
Copy link
Author

Peacock365 commented May 8, 2018

@MrAlex94

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
devtools.webide.autoinstallADBHelper - false
devtools.webide.autoinstallFxdtAdapters - false
devtools.webide.autoConnectRuntime - false

#387 and #405 seem like trivial, cosmetical fixes.

@MrAlex94
Copy link
Collaborator

MrAlex94 commented May 9, 2018

#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?

@Peacock365
Copy link
Author

Peacock365 commented May 9, 2018

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.

@grahamperrin
Copy link

@Peacock365
Copy link
Author

Peacock365 commented May 12, 2018

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):
-> https://bugzilla.mozilla.org/show_bug.cgi?id=485941
-> FIX: https://bugzilla.mozilla.org/attachment.cgi?id=8901555&action=diff

Furthermore, @MrAlex94 mentioned Bug 895096 (inconsistent widths of border-collapsed table borders), for this one there are fixes as well:
-> https://bugzilla.mozilla.org/show_bug.cgi?id=895096
-> FIXES:

A font settings issue was brought up here:
-> https://www.reddit.com/r/waterfox/comments/7q50r9/it_seems_like_font_settings_are_erroneously/?st=JCQZQ5DB&sh=fb9aa53a
This thread suggested the following bug as the culprit, but this is somewhat wrong (this bug was fixed in Firefox / Waterfox 41.0):
https://bugzilla.mozilla.org/show_bug.cgi?id=789788
Instead, the culprit seems to be this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1430798
Bug 1430798 seems to be related to something being mishandled by the fix for Bug 789788 though. See Jonathan Kew's reply in Bug 1430798 for more info.

@grahamperrin
Copy link

@Peacock365
Copy link
Author

Peacock365 commented May 12, 2018

@MrAlex94
Copy link
Collaborator

So I'm focusing on getting all the security patches done, then will revisit this after.

@Peacock365
Copy link
Author

Peacock365 commented May 14, 2018

#433 is fixed. EDIT: Fix reverted as insufficient.

@criztovyl
Copy link

criztovyl commented May 14, 2018

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. :)
(See GitHub Help: About task lists)

@grahamperrin
Copy link

Should I begin adding other open issues?

@Peacock365
Copy link
Author

Peacock365 commented May 14, 2018

@criztovyl

Sure, I did just set one up now.

@grahamperrin

Feel free to do so. The two criterions I used to track "real" issues down are as follows:

  1. The issue is not add-on related (in which case the add-on dev would be the one to approach).
  2. The issue is present on a platform Waterfox actually supports (e.g. XP/Vista problems are WONTFIX by default).

I think those two criterions make sense. I am anticipating your further entries.

@MrAlex94
Copy link
Collaborator

MrAlex94 commented Dec 4, 2019

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 :-)

@troysjanda
Copy link

expect a new current build soon?

@grahamperrin
Copy link

@laniakea64
Copy link

laniakea64 commented Dec 21, 2019

Couple things to consider adding to the list of Waterfox Current specific issues? -

  1. It is still impossible to do a stock Waterfox Current build on Linux. I still use these mozconfig customisations to unbreak building - Unable to build gecko68 branch #944 (comment)

  2. Quoting @Peacock365 -

security.family_safety.mode must be set to 0, in order to fend off potential issues due to local Man in the middle setups. See the Pale Moon 28.4.1 release notes, too: https://www.palemoon.org/releasenotes-archived.shtml Waterfox 56 had this set to 0 as well, as opposed to Firefox where this has been set to 2 since Firefox 52.

I'm not able to create pull requests for these issues, since:

  • regarding (1), I have no way to tell whether any fix I use would be too specific to my build environment,
  • regarding (2), although I do see that pref at default value of 2, I'm on Linux and that only applies to Windows.

@MrAlex94
Copy link
Collaborator

Couple things to consider adding to the list of Waterfox Current specific issues? -

1. It is still impossible to do a stock Waterfox Current build on Linux.  I still use these mozconfig customisations to unbreak building - [#944 (comment)](https://github.com/MrAlex94/Waterfox/issues/944#issuecomment-526942809)

2. Quoting @Peacock365 -

security.family_safety.mode must be set to 0, in order to fend off potential issues due to local Man in the middle setups. See the Pale Moon 28.4.1 release notes, too: https://www.palemoon.org/releasenotes-archived.shtml Waterfox 56 had this set to 0 as well, as opposed to Firefox where this has been set to 2 since Firefox 52.

I'm not able to create pull requests for these issues, since:

* regarding (1), I have no way to tell whether any fix I use would be too specific to my build environment,

* regarding (2), although I do see that pref at default value of `2`, I'm on Linux and that only applies to Windows.

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

@troysjanda
Copy link

Curious, will there be a new Current build soon? Not being pushy just saw that Classic was updated but no Current build.

@MrAlex94
Copy link
Collaborator

This is issue has been closed and replaced with this issue, since GitHub does not allow changing ownership of issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants