Closed usame-algan closed 5 days ago
β Deploy successful!
Storybook: https://hide_burger_menu--walletweb.review.5afe.dev/storybook/
Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.
Type | Occurrences | Fixable |
---|---|---|
Errors | 0 | 0 |
Warnings | 0 | 0 |
Ignored | 0 | N/A |
Report generated by eslint-plus-action
Unrelated mobile view feedback: Imo we could still display a (small) logo in the top left on mobile screens and maybe even make more space by reducing the network selector to just a logo instead of also text cc @TanyaEfremova
This analysis was generated by the Next.js Bundle Analysis action. π€
Page | Size (compressed) |
---|---|
global |
1000.63Β KB (-36Β B) |
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π‘ | Statements | 78.87% (-0.04% π») |
11574/14675 |
π΄ | Branches | 58.01% (-0.03% π») |
2807/4839 |
π‘ | Functions | 65.8% (-0.06% π») |
1845/2804 |
π’ | Lines | 80.28% (-0.05% π») |
10439/13004 |
1419 tests passing in 197 suites.
Report generated by π§ͺjest coverage report action from 0476bed59915133c97c2b17cbc5fdc01456cab55
@usame-algan fair point! There was an exploration for minimizing what we display in the mobile view, you can view it here I also added the logo, but the Safe{Wallet} one wouldn't fit, so I switched to our logomark instead.
So the burger icon doesn't show anymore for 900 to 600px width viewport. So that's correct.
Are we going to implemente the logo in its place as Tanya suggested? or should we create another ticket?
Are we going to implemente the logo in its place as Tanya suggested? or should we create another ticket?
I will create a new ticket to address the mobile header changes as we will also change the network selector slightly.
Ok, since the logo issue will be tackled in another ticket we can merge this one
What it solves
Resolves #3251
How this PR fixes it
onMenuToggle
is passed toHeader
How to test it
Screenshots
Checklist