-
Notifications
You must be signed in to change notification settings - Fork 144
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
Design System - Add containers #4370
Comments
@markmhendrickson : we had a call yesterday to clear up the scope of #4165 . We have split up the work into two issues #4370 and #4371 |
Thanks @pete-watters – can this particular issue be closed or is there more that remains for it specifically? |
This one needs to be open as the work isn't done yet. This one is closed correctly |
As part of this task, consideration needs to be given to the colour of the header as per: #4253 (comment) |
Related: #4615 (comment) |
Checking my new PR and setting the extension + popup width to As we begin to scale up, past Kapture.2023-12-20.at.12.02.40.mp4 |
@pete-watters Would it work to set the header width to 100% of the view port? |
I can give it a try for the header, that will likely work. My point is do we want to have full responsiveness on all screens from We could need to have an idea how the page responds at different widths. For example the header should stretch here but also the content width should extend too. I'll get it working well in the main sizes and then see about the interim widths |
Yes!!! that would be great: full responsiveness on all screens from sm 390px all the way to lg. cc @fabric-8 |
I've been progressing well on this:
Yesterday @mica000 and I were speaking as for some pages with a two column layout we need to make some slight design tweaks to help us make things more consistent. That overlaps with #4423 To give more context, for the key entry / password screens:
|
@pete-watters Michelly and I discussed header/footers the other day and would love to update the behaviour — Besides both being sticky, we'd also love to add a divider border to the header once content is scrolled — Here's a basic documentation of this change. Please ping me if you have any questions or if there's the need for further discussion! |
@fabric-8, OK that's no problem. Better to do it now. I had the footer being sticky so I will update it to also have a sticky header with a border showing for both on scroll. |
@markmhendrickson Indeed! Here are the designs covering the onboarding flows: https://www.figma.com/file/2stUYm67q6Tkwe31CshODA/Onboarding?type=design&node-id=1%3A16709&mode=design&t=UX0gMMYcB50sCJHM-1 |
## [6.45.0](v6.44.2...v6.45.0) (2024-08-08) ### Features * add handle network item menu, closes [#5124](#5124) ([7a778a1](7a778a1)) * **analytics:** background analytics event ([967f7b1](967f7b1)) * implement mempool api, closes leather-io/issues[#215](#215) ([0608cb8](0608cb8)) ### Bug Fixes * account change in open frames ([ac21ff8](ac21ff8)) * default to first account as useCurrentStacksAccount returns undefined, ref [#5683](#5683) ([d67d238](d67d238)) * disable stx transfer if form is not valid ([8c9dc16](8c9dc16)) * empty logo in popup mode ([10af7db](10af7db)) * fix visual bug on hover of PSBT copy, ref [#4972](#4972) ([64d2fb6](64d2fb6)) * logo box show ([0cf3dae](0cf3dae)) * mainnet faker contract address ([17d71a8](17d71a8)) * remove sign out if there are no keys ([051b1b5](051b1b5)) ### Internal * force resolution of fast-xml-parser ([bbded02](bbded02)) * import DialogHeader from monorepo ([1878330](1878330)) * post-release merge back ([8a77da4](8a77da4)) * readd fragments to help escape single quote ([8ac4349](8ac4349)) * refactor containers to make them more composable, ref [#4370](#4370) ([231842f](231842f)) * refactor switch-account to use shared context ([10254d9](10254d9)) * refactor TwoColumn to remove unneeded fragments ([b5b7988](b5b7988)) * update org name ([da5cc05](da5cc05)) * update react-virtuoso package ([c874c00](c874c00)) * update ui and query packages ([5e2547c](5e2547c))
This issue is a new version of 4165 but with a more specific scope. The task is to implement a re-usable set of containers for page
Header
andFooter
as per:https://www.figma.com/file/2MLHeIeL6XPVi3Tc2DfFCr/%E2%9D%96-Leather-%E2%80%93-Design-System?type=design&node-id=5056-60851&mode=design&t=CbvgKq8c4jj6eRZE-0
The headers should be generic but will need to have some context provided as they will show different information in different views. e.g. in
extension
view, they need to show the network / accountThis task relates to #4371 and builds upon #4165
The text was updated successfully, but these errors were encountered: