Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

IP Tracker - HTML/CSS/JS

Rayane•1,935
@RayaneBengaoui
A solution to the IP Address Tracker challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone ! 🙂

Here is my version of this challenge, any feedback/remark is appreciated ! I have a few questions:

  • The API is blocked by adblocker such as uBlock, is there a way to avoid it ?

  • I tried to hide the API key with the netlify GUI, but is there a simplest way to do it with Node.js for example ?

  • If the text returned is very long my boxes info-container__box get pushed. How can I make sure that no matter the length of the text I receive, the text fit the box ? Or dynamically adjust the font-size ?

Have a nice day ☀️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Joran Minjon•610
    @DrKlonk
    Posted about 4 years ago

    Usually the way for me to hide an api key would be as an environment variable. You can get those in a Node server by installing the package dotenv, adding a .env file and accessing it in the server by using process.env.VARIABLE_NAME. More on it here.

    Do not include it in git though, if you really want it hidden.

    Btw, I didn't do this challenge yet and have never used Netlify, so I don't know if your way is even better.

  • Bonrey•1,130
    @Bonrey
    Posted about 4 years ago

    Hello, Enayar! Great work on this challenge! 🥳 Everything works well on my laptop, although I have an adblocker turned on.

    Probably, just one little suggestion: I'd fix your html accessibility errors by adding aria-label attribute to your input field. It's a nice workaround when you don't have a label attached to the input field.

    As for the font size, I'd indeed dynamically adjust it depending on the screen width. It can be done in JavaScript like so:

    function updateFontSize() {
      let infoTexts = [dataElements.location, dataElements.isp];
      for (let i = 0; i < 2; i++) {
        if (infoTexts[i].innerText.length > 36 && window.outerWidth <= 1200) {
          infoTexts[i].style.fontSize = "0.8rem";
          infoTexts[i].style.lineHeight = "1rem";
        } else if (infoTexts[i].innerText.length > 36) {
          infoTexts[i].style.fontSize = "1.1rem";
        }
      }
    }
    

    (In fact, that's the exact snippet from my code. I recently completed this challenge myself. 😅)

    Have a nice day too! And good luck with your coding! 😉

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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