> **Regression range** > - changeset: 06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > - pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1a4d9850780709a65b7a090bfbd8eb48f209b3a7&tochange=06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > > I'm not sure which bug is the culprit looking at the changelog I think the culprit in that push log was bug 1732358, which enabled fission by default on Nightly. What's happening here is: with fission enabled, we're now painting the iframe's contents (the calendar) asynchronously from the rest of the document, since it's rendered in a separate process. The flash of pink is the background of the element in the outer document that the iframe layers on top of. And the iframe itself is transparent, so until we have its actual content to render, then the pink shows up. In other words: when we repaint the document, we don't necessarily have the iframe content available to be painted right at the same time as the rest of the outer document, so you may see whatever is "covered up" by the iframe. So this is essentially just an instance of Fission causing iframe contents to be rendered asynchronously, which is noticeable but to-be-expected. I'm reclassifying as Web Painting, and calling it WONTFIX since I think this is expected-behavior-with-fission.
Bug 1849555 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> **Regression range** > - changeset: 06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > - pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1a4d9850780709a65b7a090bfbd8eb48f209b3a7&tochange=06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > > I'm not sure which bug is the culprit looking at the changelog I think the culprit in that push log was bug 1732358, which enabled fission by default on Nightly. What's happening here is: with fission enabled, we're now painting the iframe's contents (the calendar) asynchronously from the rest of the document, since it's rendered in a separate process. The flash of pink is the background of the element in the outer document that the iframe is covering up. And the iframe itself is transparent, so until we have its actual content (from Google Calendar) to render, then the pink shows up. In other words: when we repaint the document, we don't necessarily have the iframe content available to be painted right at the same time as the rest of the outer document, so you may see whatever is "covered up" by the iframe. So this is essentially just an instance of Fission causing iframe contents to be rendered asynchronously, which is noticeable but to-be-expected. I'm reclassifying as Web Painting, and calling it WONTFIX since I think this is expected-behavior-with-fission.
> **Regression range** > - changeset: 06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > - pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1a4d9850780709a65b7a090bfbd8eb48f209b3a7&tochange=06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > > I'm not sure which bug is the culprit looking at the changelog I think the culprit in that push log was bug 1732358, which enabled fission by default on Nightly. What's happening here is: with fission enabled, we're now painting the iframe's contents (the calendar) asynchronously from the rest of the document, since it's rendered in a separate process. The flash of pink is the background of the element in the outer document that the iframe is covering up. And the iframe itself is transparent, so until we have its actual content (from Google Calendar) to render, then the pink content from the outer document shows up. In other words: when we repaint the document, we don't necessarily have the iframe content available to be painted right at the same time as the rest of the outer document, so you may see whatever is "covered up" by the iframe. So this is essentially just an instance of Fission causing iframe contents to be rendered asynchronously, which is noticeable but to-be-expected. I'm reclassifying as Web Painting, and calling it WONTFIX since I think this is expected-behavior-with-fission.
> **Regression range** > - changeset: 06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > - pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1a4d9850780709a65b7a090bfbd8eb48f209b3a7&tochange=06c7b4e2d14be1ee8050d6c1eb1ab1bab19ac3c2 > > I'm not sure which bug is the culprit looking at the changelog I think the culprit in that push log was bug 1732358, which enabled fission by default on Nightly. What's happening here is: with fission enabled, we're now painting the iframe's contents (the calendar) asynchronously from the rest of the document, since it's rendered in a separate process. The flash of pink is the background of the element in the outer document that the iframe is covering up. And the iframe itself is transparent, so until we have its actual content (from Google Calendar) to render, then the pink content from the outer document shows up. In other words: when we repaint the document, we don't necessarily have the iframe content available to be painted right at the same time as the rest of the outer document, so you may see whatever is "covered up" by the iframe for a period of time. So this is essentially just an instance of Fission causing iframe contents to be rendered asynchronously, which is noticeable but to-be-expected. I'm reclassifying as Web Painting, and calling it WONTFIX since I think this is expected-behavior-with-fission.