Download transactions button legibility

[led-boo]

🆕🐥 First Timers Only

This issue is reserved for people who have never contributed to Hedera or any open source project in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'Good First Issue' is to help you make your first contribution to Hedera.

👾 Description of the issue

1. Next to the Recent Operations header, the Download transaction button is unintuitive due its small size, lack of labelling and no tooltip. Hovering over the icon with a cursor provides no clues and the button must first be noticed and then pressed to identify its function.

2. Once pressed, the Download transaction from account window doesn't provide more information as to what is being downloaded or it's format.

Proposed Solution:

1. Increase the size of the Download transaction button with descriptive text so it is more easily identifiable and user friendly. For example; Download Transaction History

2. Provide a description as to what is being downloaded i.e format and file type (.CSV) on the Download transactions from account window. For example; Download the transaction history of account exported as a CSV file. This is useful for record keeping and tax reporting.

📋 Step by step guide to do a contribution

If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow. More information and concrete samples for shell commands for each step can be found in our CONTRIBUTING.md file.
A more detailed general documentation of the GitHub PR workflow can be found here.

• Claim this issue: Comment below that you are interested in working on the issue
• Wait for assignment: A community member with the given rights will add you as an assignee of the issue
• Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
• Check out the forked repository
• Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
• Solve the issue in your branch.
• Commit your changes: Here, it is needed to add sign-off information to the commit to accept the "Developer Certificate of Origin" (https://developercertificate.org). More details can be found in our CONTRIBUTING.md
• Start a Pull Request (PR): We have a pattern for naming pull requests that a GitHub Action checks. We use that pattern to support the creation of automatic release notes.
• Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the Hedera developer community for support.
• Wait for reviews: Members of the Hedera developer community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
• You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of the Hedera community as an open-source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽

🤔 Additional Information

If you have any questions, just ask us directly in this issue by adding a comment. You can join our community chat at Discord. A general manual about open-source contributions can be found here.

[mariyaraj]

Hey, can I work on this issue?

[hendrikebbers]

@SimiHunjan can you assign @mariyaraj pls? She will work on the issue

[Phransis]

Hello, I'm interested in this issue

[SimiHunjan]

Hi I assigned @mariyaraj as requested first. If @mariyaraj no longer wants to work on this issue I can assign @Phransis.

[hendrikebbers]

She has already created a PR: #1441

[mariyaraj]

Here also the screenshots