Sorry, I have no idea what you mean. I can’t see any difference between the fade when you click either button.
I don’t even know how I’d capture a screenshot of a fraction of a section during a fade in other than to video record it and then step through frame by frame. I’d rather watch paint dry
There is no PrtScn on my mac. To get a screenshot I have press ctrl and shift4 which enables crosshairs and then I have to drag the crosshairs around the element concerned and then release the mouse. That takes me about 5 seconds to do so would never see a fade effect.
It doesn’t seem likely because you aren’t fading out one image and then fading in another.
You say it only happens on containerb and the likely cause is that container b contains loads of ‘complex’ elements that need to be rendered and flex needs to work out where these go so you could possibly get some sort of delay on slower machines and maybe see a flash. That’s just a hypothesis as I see absolutely no difference on my machine between containera and containerb.
Note that linear gradients are well known to push the css parser to its limits. In original incarnations on Firefox you could hardly scroll the viewport when a linear gradient was applied.
These are all just observations and indeed you may have an issue but unless I can see it for myself I can’t really help.
It looks like the issue may be that when your buttons are larger than the viewport then the white flash appears (apart from that last screenshot which is a mystery). At least that’s the only way I have managed to make it happen.
You can test on your machine by removing all the buttons except 3 and then see if the flash goes away.
If you can confirm that behaviour then you can try this fix.
Note that you have two versions of that same keyframe in your code which is nonsense as there can only be one animation with that name. Use one or the other not both.
You also seem to be repeating the same gradient code for containerb when you could have merged them into one rule. I know you had two versions before but if a and b are using the same background then comma separate the rules and just supply the gradient once.
Well I’ve finally identified the problem for you so its your turn to find the solution. My solution would be to build the whole thing from the ground up rather than forever tweaking an awkward structure.
As an aside note that you don’t get a scroll bar on a real iphone so you can’t have it show. It only shows when you touch the screen and swipe. That’s not a real representation of an iphone its just a box at that size.