This does not allow our fragment to hold onto arbitrary data,
the way setRetainInstance(true) does.
/////
However,
as with onSaveInstanceState() at the activity level,
there are scenarios that onSaveInstanceState() handles that retained fragments will not,
such as terminating your process due to low memory,
yet the user later uses BACK to return to what should have been your activity (and its fragments).