Bugzilla

(In reply to Emilio Cobos Álvarez (:emilio) from comment #21)
> Did the patch make it into that beta? Presumably yes?

It seems so per the uplift made in comment 18. I've used 117.0b9 which is supposed to have the fix.

> This is hard to fix and not new (because painting remote iframes is async by nature, the content is in a different process). So while not great, it's not a regression.

Got it! I'll file a separate issue for this. 

> I'm traveling and do not have a machine that repros the first issue handy on beta, unfortunately... Is there any setting differences between the machines where you repro on where you don't?

I'm not aware of any difference setting applied on the machines, we've used clean profiles when tested on Beta and Nightly. Maybe it could be the hardware difference? I can help investigate further, let me know please.

> Presumably some other print fix on nightly also affects this, but hard to say which. I'd say let's retest when 118 is in late beta to confirm it's fixed there and there isn't any nightly-only change making this work somehow, but otherwise I wouldn't be super-concerned. Ryan, wdyt?

I'll keep an eye on the bug to retest this on 118 late Beta. 

Marking this as verified fixed on latest Nightly 118.0a1, since it does not reproduce anymore as per comment 20.

(In reply to Ryan VanderMeulen [:RyanVM] from comment #22)
> Maybe we can file a follow-up bug for any future investigation for better tracking.

I'll file one for this as well.

(In reply to Emilio Cobos Álvarez (:emilio) from comment #21)
> Did the patch make it into that beta? Presumably yes?

It seems so per the uplift made in comment 18. I've used 117.0b9 which is supposed to have the fix.

> This is hard to fix and not new (because painting remote iframes is async by nature, the content is in a different process). So while not great, it's not a regression.

Got it! I'll file a separate issue for this. 
Update: logged Bug 1849555.

> I'm traveling and do not have a machine that repros the first issue handy on beta, unfortunately... Is there any setting differences between the machines where you repro on where you don't?

I'm not aware of any difference setting applied on the machines, we've used clean profiles when tested on Beta and Nightly. Maybe it could be the hardware difference? I can help investigate further, let me know please.

> Presumably some other print fix on nightly also affects this, but hard to say which. I'd say let's retest when 118 is in late beta to confirm it's fixed there and there isn't any nightly-only change making this work somehow, but otherwise I wouldn't be super-concerned. Ryan, wdyt?

I'll keep an eye on the bug to retest this on 118 late Beta. 

Marking this as verified fixed on latest Nightly 118.0a1, since it does not reproduce anymore as per comment 20.

(In reply to Ryan VanderMeulen [:RyanVM] from comment #22)
> Maybe we can file a follow-up bug for any future investigation for better tracking.

I'll file one for this as well. 
Update: logged Bug 1849569.