Page MenuHomePhabricator

[subtask] Missing image or connection issues causes ImageOverlay to display unusable details bar
Closed, DuplicatePublic

Description

Steps to Reproduce

  1. Visit a missing image e.g. https://en.m.wikipedia.org/wiki/Barack_Obama#/media/File%3APresident_Barack_Osbama.jpg?
  2. The missing image causes a failed api response.
  3. Notice white bottom bar with "Details" link and "License information" link. Click on links.

This is closely related to T193172, but it was determined that this should be in its own card.

Expected Results

  • If links are visible, they should behave like links. If they don't, they probably shouldn't be displayed - @alexhollender please advise what we should do here - hide the entire bottom bar?

Actual Results

  • A white bar at the bottom is shown with a details button and a license information link. Clicking the details button doesn't do anything, and clicking the license information link closes the ImageOverlay. Both of these actions are unexpected.

The data returned from the API is used by ImageOverlay to fill the white bottom bar with a clickable details link and license information. When this data fails to come through, the bottom bar displays unusable links.

mobile.png (1×798 px, 95 KB)

Event Timeline

Jdlrobson renamed this task from Missing image or connection issues causes ImageOverlay to display unusable details bar to [subtask] Missing image or connection issues causes ImageOverlay to display unusable details bar .Jul 24 2018, 11:00 AM
Jdlrobson subscribed.

@nray I'd suggest writing a patch to hide it. We can double confirm with alex before merging. This closely ties in with T193172 so I'm throwing it into the existing sprint. @alexhollender please advise.

ovasileva subscribed.

Moving this back to needs analysis so that we can get some feedback from @alexhollender. Afterwards, let's estimate and pull it back in.

@Jdlrobson @nray

I'd suggest writing a patch to hide it.

Sounds good. Just to clarify:

  • the bottom bar would start out hidden
  • we would only show it if/when the image successfully loads
  • if it doesn't load we should keep it hidden (in addition to showing the error response)

is that correct?

Yup! Shall I merge this into the other task? This doesn't change the estimation imo