Skip to content
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

Make "as a download" and "obtaining a file name" more explicit #4518

Open
xyaoinum opened this issue Apr 9, 2019 · 12 comments
Open

Make "as a download" and "obtaining a file name" more explicit #4518

xyaoinum opened this issue Apr 9, 2019 · 12 comments
Labels
clarification Standard could be clearer

Comments

@xyaoinum
Copy link
Contributor

xyaoinum commented Apr 9, 2019

Followup issue for #4450:

It would be better to turn as a download into a more explicit list of steps (if to be aborted, if the resource was successfully obtained, if need a file name, etc.).

Also it would be better to make "obtaining a file name" a more explicit algorithm on its own. Currently the algorithm simply comes after as a download and doesn't have a explicit name.

@annevk annevk added clarification Standard could be clearer good first issue Ideal for someone new to a WHATWG standard or software project labels Apr 10, 2019
@Catalyst497
Copy link

I would like to work on this one. Is it open?

@annevk
Copy link
Member

annevk commented May 31, 2022

Yes, this is still a problem worthy of addressing.

@Catalyst497
Copy link

Ok. How do I start? I'm a first-timer

@yashdev9274

This comment was marked as duplicate.

@kartikver15gr8

This comment was marked as duplicate.

@RJ025

This comment was marked as duplicate.

@annevk
Copy link
Member

annevk commented Sep 21, 2022

The issue is still open, but if you want to address it you'll have to figure out from the README and other instructions in the repository how go about creating a PR. Unfortunately nobody has the bandwidth to walk someone through this at the moment.

@Chetan-Salunke

This comment was marked as spam.

@utkarsh-shrivastav77

This comment was marked as spam.

@Lamma-maihadisi

This comment was marked as spam.

@Aksshay88

This comment was marked as duplicate.

@gitclonegaurang

This comment was marked as spam.

@annevk annevk removed the good first issue Ideal for someone new to a WHATWG standard or software project label Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer
Development

No branches or pull requests