when you’re using a placebo-tier fork of a really ancient firefox code made and “maintained” by a creepy furry, things not working quite right should be expected behavior.
i literally can’t think of a single legitimate reason to use any of those clones, i.e. waterfox, pale moon, whatever else.
In case anyone in the future wants to debug a Safari issue without having an Apple device, you can use GNOME Web (aka Epiphany). It uses the same WebKit as Safari with pretty much the same bugs and missing functionality.
Incidentally, I think line 595 of tt-rss.js is wrong. It catches the failure to initialize App and then uses App. I hate window.alert as much as the next web dev, but I think it might be appropriate here instead of getting stuck on “Loading, please wait”?
FWIW, that last error that @martywd reported on Pale Moon also happens to me on Firefox 71.0 (64bit) (latest release on Win10). Simply resizing the window by opening the dev console fixes it. Sorry for hijacking this thread further.
Damn! Just checked firefox 71 (which I rarely use) on a windows 7 machine. Same issue as I reported w/ Pale Moon and now that @f0ff886f and @AngryChris type about.
fwiw,here’s a link to conole output from firefox 71 (64-bit) in safe mode on the windows machine. The console output is from tt-rss login screen on firefox, to main screen , to Preferences, F11 press twice to get the screen tab to redraw properly, and then exit Preferences.
.
I’m seeing this on Firefox 68.3.0 ESR in Debian Buster.
This was definitely not a problem as recent as last week. I don’t go into Preferences often (which is why I didn’t notice sooner) but I have been in there in the last week so it’s for sure a recent commit. I don’t have time to troubleshoot at the moment.
A quick look in the inspector seems to suggest that div containers inside #main are being set with a height that’s too short (57px in my case) so the content doesn’t appear. Resizing anything triggers Dojo to recalculate the layout and set the proper size.
it’s likely a race condition between dojo initializing and css stylesheet being replaced by nigh mode detection, chrome is either faster or smarter at this so it’s not visible there.
well, apparently this happens because firefox has an asynchronous loader for CSS, while blink-based browsers block on CSS load. so, on startup, dojo gets confused because execution continues while CSS is still reloading because of day/night change.
it’s kinda sad, while not surpising, that what started as a 10 LOC quality of life patch turned into a huge ugly monstrosity.
The latest git commit (07f4878d59a7459472e66a2ba0c1c0413232107e) completely breaks Tiny Tiny RSS for me on Firefox 71.0, Chromium 78.0.3904.108, and Google Chrome 79.0.3945.79 on Ubuntu 18.04. With that commit all the browsers render an empty page after login. The page title is set correctly, but even after an reloading the page without cache, the page stays empty.
After reverting to the previous commit (0d6add5d7f9475d60330f233a6b62f9bb81d01c0), rendering is back to normal.