UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

Steps to reproduce the problem:
I have an idea for the Aw Snap screen:
Make it transparent!
The idea is OK we need to tell the user the web page he was reading is
frozen, stuck, etc. But we shouldn't rob him of his right to copy
his bank account numbers etc. off of what remains of his screen.
And indeed let him scroll it around too. So maybe have the Aw Snap
thing just float around... The idea is certainly there was still some
data known to the browser when the problem happened. So don't just throw
up the wall and "rob" the user of what he was looking at.
"Well yes but then the user will blame us for an improperly operating
web page." (OK, then, at the bottom of the Aw Snap page say: "would you
like to see what the page looked like just before it crashed?" And if
yes, then "Do you understand that the page is dead now...?")
Also bug reporters could say "this is what the screen looked like just
before Aw Snap."

What is the expected behavior?

What went wrong?
User could have copied that important order confirmation number that was sitting on the screen before it crashed.

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? No 

Chrome version: 69.0.3497.92  Channel: n/a
OS Version: 
Flash Version: