Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Responsive Mob\Desk Design using Vanilla HTML,CSS(flexbox),JS

fetch
GHNetCode•170
@GHNetCode
A solution to the URL shortening API landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello to all you wonderful Developers out there and A Big THANK YOU to FrontEndMentor for this challenge! This App has been tested on Browsers -: Brave, Chrome and Edge.. I have added animating buttons and a configuration where you can just update maxRows "param\var" to the number desired of links needed. When the number of links has exceeded it will notify the user of the oldest link that will be overwritten to be saved if needed. I have left a few comments in the code to help others and myself along the way if ever needed. The things i learned and solved about this challenge.

  1. Ensuring there is consistency between element Id`s and localStorage Keys.
  2. The ability to be able to clone elements without the need of writing out repetitive code where prepping the template before it is cloned is needed.
  3. Using the clipboard unfortunately i bumped into issues using the "pointerdown" event where i was receiving the message "Must be handling a user gesture to use custom clipboard". Here i found out after 3 or 4 days of investigating that simply changing this to the "click" event has resolved this issue. I hope this helps someone.
  4. Lastly, I presume when working with localStorage in the future it would be recommended to have just 1 local storage Key and have all the data\objects in it instead of separate keys. Please do have a go and let me know what you think, your feedback will be much appreciated. All the Best, M.
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on GHNetCode's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.