Catalin, can you still reproduce this? (I can't, but I'm not sure I have the right setup.) Also: if you can reproduce, maybe we should dupe this to bug 1659413 and reopen that bug? The two bugs have the same STR/symptoms as far as I can tell. (It looks like bug 1659413 was closed in September 2020 as WORKSFORME because we thought it wasn't reproducible anymore (bug 1659413 comment 8 - 9), and then Catalin was able to reproduce 2 months later in November 2020 and filed this bug as a result instead of reopening the original bug. I think a new bug [this one] would make sense if we really think it was fixed and then broke again, but it's not clear to me that that's what happened.)
Bug 1679392 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Catalin, can you still reproduce this? (I can't, but I'm not sure I have the right setup.) Also: if you can reproduce, maybe we should dupe this to bug 1659413 and reopen that bug? The two bugs have the same STR/symptoms as far as I can tell. (It looks like bug 1659413 was closed in September 2020 as WORKSFORME because we thought it wasn't reproducible anymore (bug 1659413 comment 8 - 9), and then Catalin was able to reproduce 2 months later in November 2020 and filed this bug as a result instead of reopening the original bug. I think a new bug [this one] would make sense if we really think it was fixed and then broke again, but it's not clear to me that it really was fixed; it seems like maybe it was just difficult/rare-to-reproduce.)