Fix #19872 : Responsiveness in the about section was inaccurate.

[rahat2134]

Overview

1. This PR fixes or fixes part of [BUG]: The Access the android app button should be completely visible #19872 .
2. This PR does the following: Responsiveness in the about section was inaccurate in access the android button specially. It was not visible at some widths. Resolve all those issues.

Essential Checklist

• The PR title starts with "Fix #bugnum: " or "Fix part of #bugnum: ...", followed by a short, clear summary of the changes.
• I have followed the instructions for making a code change.
• I have assigned the correct reviewers to this PR (or will leave a comment with the phrase "@{{reviewer_username}} PTAL" if I don't have permissions to assign reviewers directly).
• The linter/Karma presubmit checks pass on my local machine, and my PR follows the coding style guide).
• "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)

Proof that changes are correct

screen-capture.20.webm

PR Pointers

• Never force push! If you do, your PR will be closed.
• To reply to reviewers, follow these instructions: https://github.com/oppia/oppia/wiki/Make-a-pull-request#step-5-address-review-comments-until-all-reviewers-approve
• Some e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.
• See the Code Owner's wiki page for what code owners will expect.

[rahat2134]

@nikitaevg PTAL.

[oppiabot]

Hi @rahat2134 please assign the required reviewer(s) for this PR. Thanks!

[rahat2134]

@nikitaevg PTAL.

[rahat2134]

@Nik-09 PTAL untill @nikitaevg is back. I think he is busy.

[oppiabot]

Unassigning @rahat2134 since a re-review was requested. @rahat2134, please make sure you have addressed all review comments. Thanks!

[nikitaevg]

Hi @rahat2134

Please allow at least 2 days for reviewers to respond before pinging, let alone reassigning to others. Most people do this in their spare time, not every day

[nikitaevg]

I don't think it's a good approach to fix the issue. Let's fix it properly. Why the padding or padding-top should be different for 960px, 868px, 698px etc? We have a simple task - the button should be within this container for all widths. Please find a solution that fixes the task without so many if-s, this is a too dirty solution.

[oppiabot]

Unassigning @nikitaevg since the review is done.

[oppiabot]

Hi @rahat2134, it looks like some changes were requested on this pull request by @nikitaevg. PTAL. Thanks!

[oppiabot]

Hi @rahat2134, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[oppiabot]

Hi @rahat2134, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[oppiabot]

Hi @rahat2134, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[oppiabot]

Hi @rahat2134, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[oppiabot]

Hi @rahat2134, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[oppiabot]

Hi @rahat2134, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!