Thunderbird 102.13.0 with uBO 1.57.0+
rcalixte opened this issue · 2 comments
Prerequisites
- I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
- This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
- This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
- I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
- The issue is not present after disabling uBO in the browser.
- I checked the documentation to understand that the issue I am reporting is not normal behavior.
I tried to reproduce the issue when...
- uBO is the only extension.
- uBO uses default lists and settings.
- using a new, unmodified browser profile.
Description
After updating to 1.57.0 and then 1.57.2, the uBO icons turns yellow and seems to be in some kind of cycle. The same issue prevents extension options and feed message bodies from rendering (HTML web pages, not summaries). There is just a constant "Loading" message without the page loading. There are no errors or outputs I can see. Reverting to 1.56.0 fixes the issue. It is repeatable but I haven't had a chance to dig through the release notes to see what changed quite yet.
A specific URL where the issue occurs.
Any RSS account e.g. Slashdot's RSS feed - http://slashdot.org/rss/slashdot.rssSteps to Reproduce
- Install 1.57.0 or 1.57.2 from the Release assets.
- Try to open the extension options or any feed item with the web view.
- Thunderbird restarts are optional.
Expected behavior
Extension options are accessible along with feed contents.
Actual behavior
No content loads for feed items (other than the text summary) and the extension options are also inaccessible. The uBO icon in the toolbar also remains yellow. Duration has no impact on this.
uBO version
1.57.x
Browser name and version
Thunderbird 102.13.0 (Flatpak)
Operating System and version
Ubuntu 22.04
Maybe related to gorhill/uBlock@f940841. If so, this is fixed in dev build.