raymes: Do you remember who did the current PDF Viewer UX?

I think it was someone named Cody who I don't think is working on Chrome anymore (can't find references in my inbox). tbuckley was somewhat involved at the time.

Also +tsergeant who was heavily involved in the design.

Yep, csielawa@ (no longer on Chrome) worked on the visuals for MD PDF Viewer. +bettes has led the other MD WebUI redesigns. The goal of the auto-hiding UI was to focus on the PDF as much as possible.

@dsinclair to make this more concrete, could you share an example case where having the UI disappear caused a problem?

I personally find it distracting, and have missed that controls existed because they disappeared off the screen (I didn't know the bookmarks button was there for the longest time).

The original issue I received which I filed above was:

  controls disappear making it unfriendly for swapping between windows and then expecting
  to use them (extra click + mouse movement to make the controls show on a mac)

I also wonder how well the auto-hiding controls work from an accessibility perspective.

Had a CL disabling the hide behavior of the controls, leaving them on screen. It causes some other issues though, such as presentation mode looking bad and the zoom buttons hiding part of the text if zoomed in.

I think we should just close these bugs and leave it as is.