Hello @nightsky30, out of mild curiosity, at Steam -> Settings -> Interface is Enable GPU accelerated rendering in web views (requires restart) checked and if it is, does switching it have an effect on this issue?
GPU Acceleration for rendering web views is currently disabled due to issues I am having with #6549, but I can enable it and retest.
Re-enabling GPU Acceleration for rendering web views does correct this issue.
I've also noted that the black windows issue appears to be fixed in #6549 when running the latest beta and NVIDIA drivers. I did everything I could think of to try and cause the bug to surface.
@nightsky30 https://github.com/ValveSoftware/steam-for-linux/issues/6715
Be aware of this , Steam client can fill your vram very quickly after interacting a few steam windows , after resizing some windows etc and it is permanent. Won't go away until next reboot.
@Leopard1907 Closing Steam empties my RX 480's VRAM; restarting Steam seems to be enough on my end. Thanks for bringing this up though, I wouldn't have known otherwise.
Hello @nightsky30, are you still experiencing this issue on an up to date system?
It doesn't appear so. I'm not generally having redraw issues any longer even with Re-enabling GPU Acceleration for rendering web views disabled. I did manage to get the featured store page to fail to load once after disabling the setting and restarting. It just didn't render anything until the window was resized. Can't reproduce it though.

Your system information
https://gist.github.com/nightsky30/e29fd06661e25d83fe4ae3aaf4c609e3
Please describe your issue in as much detail as possible:
There appear to be excessive redraw issues when on the Holiday Market page and then clicking on one of the items in the user's "inbox" menu like viewing new comments or inventory items.
This doesn't happen when the Holiday Market page is being loaded, but rather after it has loaded and the user is leaving the market to access their inventory, etc. Sometimes the redraw is less extensive, sometimes worse. I've not yet encountered this anywhere else.
Steps for reproducing this issue: