Tiny Tiny RSS needs window.requestIdleCallback but it’s not supported in Safari. You used to be able to enable it by turning on the “requestIdleCallback” flag under “Experimental Features” but as of version 16.4.1 (Mac and mobile Safari), that option is gone. It’s also gone from Safari Technology Preview.
To use Safari (or any browser on iOS/iPadOS), follow the advice given before:
basically just replace the compose file from static-dockerhub branch (above) in the same directory so it would pull images instead of trying to build your own.
alternatively, pull latest docker scripts and investigate why latest source is not pulled while building.
but seriously, just use docker hub images. there’s no need to use anything else now that they’re multiplatform.
Well crap, it sure looks like the fault is mine. I have been using using a docker-compose.override.yml in order to configure volumes so I can add my own themes and plugins as well as the local-overrides.js file for the Safari fix (plus some minor development in the past but it has been a long time.) I was using the dynamic build instructions from the Docker FAQ.
What is the recommended procedure for installing custom themes/scripts if using static-dockerhub? The Docker FAQ mentions modifying docker-compose.yml changing (I assume):
Sorry, but I really am still a Docker newbie, just trying to tread lightly so I don’t run into the same issues converting from dynamic to static as some other folks.
it should work the same, the only difference is that tt-rss source is not pulled from git. however, i would instead try to map themes.local & plugins.local instead of tt-rss/ so that main tt-rss source is guaranteed to update properly. it’s easy to screw up permissions on bind mounts. not sure if it’ll work or not.
Sorry, when you say updater: is the same, do you mean the same as in the shipped docker-compose.yml or the same as in the dynamic image for development docker-compose.override.yml in the FAQ? Or the same volumes change as is in the app: (which seems most likely?)
Well let me say you’ve been a great help as always! But let me also say I’m an idiot because now I recall the other reason I use the dynamic development build in the first place (not just themes/plugins) … I always make a tiny tweak in js/Article.js that prevents the vertical snapping (it’s because of the way I go through feeds, start at the bottom and CTRL-UP) … it was my fault it wouldn’t update because my modification to Article.js was blocking the git pull part of the build.
There was no notice when doing the docker-compose up --build -d so I didn’t realize it until browsing into the static volume and running git commands from there. Sorry, completely and totally my fault and I’m good now after unstuffing my own mess.
My modification to Article.js is to comment line 429:
Thanks Fox. I’ve looked (briefly) at how to do this and so far it was easier to just maintain a one-off but maybe I’ll get some time to devote to this.
It has to do with where the article opens when “opening” a collapsed headline. Say you have a long list of collapsed headlines, when you “open” a collapsed headline in the middle of the viewing portal, my eye expects it to push the content down but not scroll to the top of the viewing portal. Commenting this line prevents that. Essentially tracking the headlines is easier without it jumping around if I open an article. Well, let me rephrase, only the lower headlines move when opening a collapsed article and everything returns to its previous position when closing an article. Hard to explain, but does that make sense?