On Thu, 2020-09-03 at 22:43 +0200, Raúl Sánchez Siles wrote: > Fortunately 80.0.1-1 came around and this bug has been somehow > fixed or not exposed. This is what I can tell so far. Let me know if > I can provide any more helpful information.
yes... that seems to fix it... Cheers, Chris.
