I've noticed that e.g. the brand overview pages on Zalando (i.e. like https://www.zalando.de/s-oliver/) fail to load because they're trying to push too much history state data onto the stack and are running into the old Firefox limit which currently still persists in Waterfox. So for compatibility reasons I guess we have no choice and need to mirror Firefox here (which in turn is stuck because Chrome apparently has no fixed limit at all…).
At least we're already compressing the on-disk session store files just like Firefox does, which should mitigate this potential size increase in session history for that kind of pages.
I've noticed that e.g. the brand overview pages on Zalando (i.e. like https://www.zalando.de/s-oliver/) fail to load because they're trying to push too much history state data onto the stack and are running into the old Firefox limit which currently still persists in Waterfox. So for compatibility reasons I guess we have no choice and need to mirror Firefox here (which in turn is stuck because Chrome apparently has no fixed limit at all…).
At least we're already compressing the on-disk session store files just like Firefox does, which should mitigate this potential size increase in session history for that kind of pages.