-
Notifications
You must be signed in to change notification settings - Fork 132
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
[Bug]: Add responsivness #402
Comments
Hey @k-deepak04, Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. Please make sure you have given us as much context as possible. |
oh...but yesterday i was getting that see the ss is with date and time, maybe you are checking on your local host, please check the deployed link, maybe while adding pr this happend..... @swapnilsparsh please let me know the updates :) |
@k-deepak04 I have checked on production website, but nothing seems to be wrong on Chrome But when I am checking on Microsoft Edge then there is the issue which you are telling |
Hey @k-deepak04, thank you for raising an issue. I have assigned the issue to you. You can now start working on it. If you encounter any problems, feel free to connect with us. |
okay so i'll try to fix it and check on both chrome and edge :) |
@swapnilsparsh for me it's on google too and i figured out what's the issue that space is for ads so it's visible in edge and chrome for me but not in brave as ads are blocked so please let me know what to do , shall we keep that or change something? |
@k-deepak04 Thank you for identifying the issue. I have turned off the ads that's why there are some issues. Will fix them from my end soon. |
Hey @k-deepak04, This issue is closed. |
Description
Too much space is seen in the mobile view
Expected Behavior
this must be the expected behaviour
Show us the trouble with screenshots
n/a
Which browsers are affected?
No response
Which OS are affected?
No response
Enter the version of your web browser
n/a
Device?
No response
Record
The text was updated successfully, but these errors were encountered: