I solved both issues according to my knowledge. So, you can see
Fixes # (issue)
Type of change
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
How Has This Been Tested?
My issues is related to responsive navbar so i try to implement all possible testing means i try this functionalities in different kind of mobile with the help of google responsvie funcationality.
Test Configuration:
Firmware version:
Hardware:
Toolchain:
SDK:
Checklist:
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
Description
I solved both issues according to my knowledge. So, you can see
Fixes # (issue)
Type of change
How Has This Been Tested?
My issues is related to responsive navbar so i try to implement all possible testing means i try this functionalities in different kind of mobile with the help of google responsvie funcationality.
Test Configuration:
Checklist: