Updates to border radius generator tool
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 647
- Forks
- 830
- PR merge metrics
- No merged PRs in 30d
Description
What was incorrect, unhelpful, or incomplete?
This stems from the discussion I started concerning the tools on MDN Web Docs. Please read the discussion for more details and context.
There are a couple of common problems between these tools and issues filed here. This issue will track the work on addressing the relevant issues and do a bit of a rewrite of the border radius generator.
Known issues
None
Common issues
- Ensure that the tool is responsive and usable on as many platforms and devices as possible.
- Rewrite the JS to use modern syntax without introducing the need for polyfills
The work will be split up into two to three separate pull requests. The first will address the responsiveness, the second the JS, and the last any existing issues that were not already fixed by the JS updates.
Reviewers for the work will be between @caugner and @LeoMcA
What did you expect to see?
The tool is responsive and usable across viewports and devices. The code has been updated and is in a better state to ensure they can be more easily maintained going forward.
Do you have any supporting links, references, or citations?
https://github.com/orgs/mdn/discussions/674
Do you have anything more you want to share?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the linked Border-radius generator page and read discussion 674 for the intended scope and split between pull requests. Verify the tool across viewports and devices, then review its JavaScript for the modernization work; done means responsive behavior and maintainable modern JavaScript without polyfills.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, javascript
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100