Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
3
Comments
1

Sebastián Farías

@SebaFariasChile80 points

Self-taught full stack developer

Latest solutions

  • React using Context and reading data from a JSON


    Sebastián Farías•80
    Submitted almost 5 years ago

    1 comment
  • Mobile first using Mapbox and the IP Geolocation API by IPify


    Sebastián Farías•80
    Submitted almost 5 years ago

    0 comments
  • Mobile first using linear functions and flexbox


    Sebastián Farías•80
    Submitted almost 5 years ago

    0 comments

Latest comments

  • David Parsons•205
    @Davros2014
    Submitted almost 5 years ago

    IP address tracker - html/css/js

    1
    Sebastián Farías•80
    @SebaFarias
    Posted almost 5 years ago

    I noticed that in the mobile layout, your trackerOutput panel overlaps the search bar, maybe this could help:

    You should nest your trackerOutput panel inside your header section, that way, if you add "position: relative;" propety to the header and "top: 170px;"(or something around it) to the trackerOutput it should work fine on the mobile view.

    I am asuming you made this for semantic reasons, not wanting to have a section nested inside another section but i think, in this case, that is fine.

    Although by semantics maybe the titles "IP Address, Location, Timezone and ISP" should be h2 and the values an h3 or p, even if they are smaller.

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

Beta Member

This badge is a shoutout to the early members of our community. They've been around since the early days, putting up with (and reporting!) bugs and adjusting to big UX overhauls!

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

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

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

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

Oops! 😬

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

Log in with GitHub