Page MenuHomePhabricator

[L] Improve the opening and closing of search previews on Mobile
Closed, ResolvedPublic

Description

This ticket is to improve the opening and closing behaviour/animations for search preview to:

  • reduce too much movement of content on screen
  • reduce the perceived load time of the content

Doing so will not only improve loading experience but also help us decide if we should pursue with opening multiple previews or not in T321590

Things to improve:

Opening preview

  • Show search preview loading skeleton (as prescribed in this ticket T321944) or the content if it is already available, right away instead of top-down animation that we currently have.
    • Mobile preview loading should follow similar patterns as the desktop preview box which appears without animation and shows skeletons for additional content loading.
      • In addition it would be good if the skeleton/content fades in.
  • Open to full height immediately with content skeleton.
    • This is with the assumptions that most top results will have preview.
      • Minimize the preview to show the current "no preview" message if the preview does not exist.

Closing preview

  • Hide the preview right away (instead of bottom up animation) and then slide the page content up.
    • In addition it would be good if the skeleton/content fades out.
  • While closing the preview could we use the ease-in effect to slide up the content.

Event Timeline

CBogen renamed this task from Improve the opening and closing of search previews on Mobile to [L] Improve the opening and closing of search previews on Mobile .Mar 8 2023, 6:00 PM

Change 904523 had a related patch set uploaded (by Simone Cuomo; author: Simone Cuomo):

[mediawiki/extensions/SearchVue@master] Improve the opening and closing of search previews on Mobile

https://gerrit.wikimedia.org/r/904523

Change 904523 merged by jenkins-bot:

[mediawiki/extensions/SearchVue@master] Improve the opening and closing of search previews on Mobile

https://gerrit.wikimedia.org/r/904523

@Sneha - the case when there is no content to preview (listed below as a no content to preview case) - the skeleton is still shown while loading. Is it ok
betalabs search=mavetuna&quickView=Mavetuna+70+4.
You may compare it with the following search idwiki search=Gabut&quickView=Gabut. The behavior for the no content to preview case is still the same between production and betalabs.


The transition is in the current production (wmf.6/7 with network throttling).

idwiki wmf.7betalabs
lead img/related img are present
mobile_animation_lead img3.gif (685×385 px, 479 KB)
beta mobile_animation_lead img4.gif (685×385 px, 640 KB)
no lead img
mobile_animation_no lead img3.gif (685×385 px, 92 KB)
beta mobile_animation_no img4.gif (685×385 px, 116 KB)
no content to preview
mobile_animation_no preview3.gif (685×385 px, 81 KB)
beta mobile_animation_no img3.gif (685×385 px, 107 KB)

@Etonkovidova we replaced the previous "spinner" loading indicator with skeletons so that is why the skeleton is showing in all cases. I assume we would not know if the preview exists or not until we load it. If that is true it is okay to see the skeleton first. But if that is not true and we know beforehand we could show the "No content to preview" message right away. But I am guessing the former is true. @SimoneThisDot can confirm.

@Etonkovidova we replaced the previous "spinner" loading indicator with skeletons so that is why the skeleton is showing in all cases. I assume we would not know if the preview exists or not until we load it. If that is true it is okay to see the skeleton first. But if that is not true and we know beforehand we could show the "No content to preview" message right away. But I am guessing the former is true. @SimoneThisDot can confirm.

Thank you, @Sneha! I agree - the case with "no content to preview" is rather minor. I've updated my comment with mentioning that gifs were done with net throttling. With normal network connectivity, all cases look smooth and issues-free.

Am I correct to assume that this is ok to move forward or would you like me to do any followup action on this task?

Am I correct to assume that this is ok to move forward or would you like me to do any followup action on this task?

I ew-checked in wmf.11 - all works as per specs; the gifs in https://phabricator.wikimedia.org/T329241#8827962 match the current production behavior.