Bug 5969 - Hidden columns should not be showed one moment in time.
Summary: Hidden columns should not be showed one moment in time.
Status: CLOSED NOTABUG
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Jessica
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-03-14 09:39 UTC by Yuan Sun
Modified: 2014-03-17 02:07 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
screenshot.tar.gz (690.34 KB, application/x-gzip)
2014-03-14 09:40 UTC, Yuan Sun
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yuan Sun 2014-03-14 09:39:52 UTC
Hidden columns should not be showed one moment in time.
Start up toaster.
All builds-> core-image-sato qemux86->packages
Only default columns are showed.
Click a page button(such as 6) to enter another page of package link.
A splash screen occurs and all columns(hidden and unhidden columns) are showed.
Acutally hidden columns should not be showed.
A second later,only default columns are showed.
Comment 1 Yuan Sun 2014-03-14 09:40:21 UTC
Created attachment 1815 [details]
screenshot.tar.gz
Comment 2 Belen Barros Pena 2014-03-14 11:53:01 UTC
Hi Yuan,

This is not a bug, but related to the way we have implemented the "edit columns" menu: instead of hiding all columns by default, then show the ones selected in the "Edit columns" menu, we show all columns by default, then hide the ones not selected in the "Edit columns" menu. This makes sure the interface does not fall apart if javacript is not (well) supported by the client.

I've also been told that a short animation was added to the column hiding/showing to avoid a flickering effect on the screen. 

Both things together account for the effect you see.
Comment 3 Yuan Sun 2014-03-17 02:07:39 UTC
Well. I would close the bug. But I think we need imporve the user experience.