(In reply to Bodea Daniel [:danibodea] from comment #16) > (a new changeset was pushed to inbound in comment 15, maybe something was missing from the push?) [...] > I will wait for the inbound push to get updated in the latest Nightly and retest. Thank you. I don't actually know what comment 15 was about -- that seems to have been posted by mistake. It's the exact same commit from comment 6 (with datestamp Oct 30th), so there's nothing new there. I'm going to mark it as "offtopic" to auto-hide it since it's not relevant and was likely posted by mistake and causes confusion. I'm also confused -- you said: > APPARENTLY fixed builds: > Nightly v72.0a1 (2019-11-04) -> issue still occurs So to clarify, you **are** seeing the issue happen in that build? (and by "apparently fixed" you mean the build-is-after-the-fix-date, but the issue's not fixed?) Could you post a screenshot of the issue that you're seeing there, just to sanity check that it's the same problem? I tested locally on Win10 and I'm not seeing the issue in recent nightlies (e.g. the latest nightly as well as the one from Nov 1st).
Bug 1587127 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Bodea Daniel [:danibodea] from comment #16) > (a new changeset was pushed to inbound in comment 15, maybe something was missing from the push?) [...] > I will wait for the inbound push to get updated in the latest Nightly and retest. Thank you. I don't actually know what comment 15 was about -- that seems to have been posted by mistake. It's the exact same commit-hash from comment 6, and it shows datestamp Oct 30th if you click through, with Oct 31 as the date for its push [to m-i] if you click through its "push id" link. So there's nothing new there. I'm going to mark it as "offtopic" to auto-hide it since it's not relevant and was likely posted by mistake (or at least on a many-day delay) and it causes confusion about when things happened here. I'm also confused -- you said: > APPARENTLY fixed builds: > Nightly v72.0a1 (2019-11-04) -> issue still occurs So to clarify, you **are** seeing the issue happen in that build? (and by "apparently fixed" you mean the build-is-after-the-fix-date, but the issue's not fixed?) Could you post a screenshot of the issue that you're seeing there, just to sanity check that it's the same problem? I tested locally on Win10 and I'm not seeing the issue in recent nightlies (e.g. the latest nightly as well as the one from Nov 1st).