-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
[change] Eliminate redundancy of header HTML #314
Comments
Hi, I would like to work on this issue, please tell me how to proceed :) |
Hi @Red-0111, Please check openwisp-wifi-login-pages/client/components/header/header.js Lines 145 to 148 in f2af7f1
desktop: openwisp-wifi-login-pages/client/components/header/header.js Lines 59 to 62 in f2af7f1
In this issue, it is mentioned to get rid of one header using CSS. |
Hello @Red-0111, Are you working on this? |
Yes please give me some time I am trying to figure it out. |
Great, If you need any help feel free to ask 👍 |
Is anyone working on this? |
Yes, it would be great to have some help :) |
What issues are you facing @Red-0111? |
While running the headless test for yarn the test suites fail and it shows command failed with exit code 1. I tried searching the issue on internet but nothing worked. |
Have you tried the correct way of running browser-test as described in README? @Red-0111 If you have implemented this, please make a draft pull request. I will review the PR and then can tell more about the error. |
Yes I followed the same steps as in the README. I was installing dependencies so what should I make the pull request for? |
I thought you had implemented the changes and now trying to run tests before creating PR. It will be better if you can provide some details about the error (screenshots). Also before running tests had you run the command yarn setup? @Red-0111 |
@Red-0111 I suggest using the OpenWISP support chat to coordinate better. |
Yeah sure |
The header HTML is kind of duplicated, once is a desktop version and one is a mobile version.
I wonder if we can avoid this and handle everything with CSS.
It's kind of painful to customize this part because of this duplication (double amount of work).
The text was updated successfully, but these errors were encountered: