New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup shield UI polish #561
Comments
I'm a little lost why we still use tables, they don't appear to do anything but hinder layout and don't really add much semantic meaning either. Notable changes:
|
After the review process, now we have the final updated screens for shield UI Screens And here are the specs Image assets Thanks! Let me know if you need any other assets. |
@fangshih thanks! I'm not sure what the second panel is for labelled "Edit Current Tab Panel". The edit panel is actually "Remove Default Panel" and the assigning is actually in the first panel. |
@jonathanKingston Yes, you are right. I've removed that panel. It was from the older version spec. Thanks for reminding. : ) |
You have to click back. This was half agreed on with the changes to the
edit screen. @groovecoder were you expecting save and cancel here as
before? In a way that makes edit more confusing.
…On Tue, 13 Jun 2017, 19:46 luke crouch, ***@***.***> wrote:
Just ran the latest code and I can't see the button to create a new
container anymore? 😢
[image: image]
<https://user-images.githubusercontent.com/71928/27098917-ba5a79b8-503e-11e7-859a-5519dcc3d96e.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#561 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUsLE5pp_HbKd8cquZPu8edOwpS1VBtks5sDtkSgaJpZM4NrDCF>
.
|
Oh yes, I was expecting Save/Cancel buttons. But if the changes take effect on the |
@groovecoder That was discussed before. There are several reasons we decided to remove Save/Cancel:
Besides, I noticed the layout is different from the current measurement, could you update the layout to make it more intense? |
@ChenMorpheus yeah agreed that tightening of the layout hasn't been completed. It might have to be post release because of timescales. I can add a "Back and Save" title on the arrow. I suspect we will get complaints, especially on the new version however we can always refactor. |
Which PR(s) finish this issue? |
We need to make sure the current UI matches the following:
Current UI:
The text was updated successfully, but these errors were encountered: