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

Sameema Nasrin

@SameemaNasrinIndia130 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • Responsive Calculator App using Flexbox, Media query and DOM operation

    #pure-css

    Sameema Nasrin•130
    Submitted 7 months ago

    I'm looking for a cleaner way to handle dynamic content resizing. Currently, I'm using a max-width with overflow: hidden, but it feels like more of a workaround than a permanent solution. I’m wondering if there’s a more elegant and flexible layout approach that could better handle this, without compromising the responsiveness of the design. Any suggestions or guidance on how to improve this would be really helpful!


    3 comments
  • Responsive Bento Grid using CSS Grid and Flexbox

    #pure-css

    Sameema Nasrin•130
    Submitted 7 months ago

    The efficiency of my CSS Grid and Flexbox implementation — are there ways to optimize it further?


    1 comment
  • All functionalities logic in vanilla js


    Sameema Nasrin•130
    Submitted about 2 years ago

    0 comments
  • Used media query for responsiveness.


    Sameema Nasrin•130
    Submitted about 2 years ago

    0 comments

Latest comments

  • Sameema Nasrin•130
    @SameemaNasrin
    Submitted 7 months ago
    What are you most proud of, and what would you do differently next time?

    I’m really proud of the fact that I managed to quickly find a workaround for the resizing issue in my result div. I added a max-width and set overflow: hidden, which stopped the layout from breaking when the numbers got too large. It’s not perfect, but it did the job for now. Next time, I’d probably try to come up with a more scalable solution that doesn’t limit the content visibility. Something more dynamic that adapts as the number grows would be ideal, so the layout stays intact without cutting off any data.

    What challenges did you encounter, and how did you overcome them?

    The biggest challenge was that as the numbers in the result div grew, they stretched the container, throwing off the layout and making things look messy. To fix this, I used max-width to cap the div size and added overflow: hidden to prevent the content from overflowing. It was a quick fix, but I realized it’s not the most elegant or long-term solution, so I’d like to improve it moving forward.

    What specific areas of your project would you like help with?

    I'm looking for a cleaner way to handle dynamic content resizing. Currently, I'm using a max-width with overflow: hidden, but it feels like more of a workaround than a permanent solution. I’m wondering if there’s a more elegant and flexible layout approach that could better handle this, without compromising the responsiveness of the design. Any suggestions or guidance on how to improve this would be really helpful!

    Responsive Calculator App using Flexbox, Media query and DOM operation

    #pure-css
    3
    Sameema Nasrin•130
    @SameemaNasrin
    Posted 7 months ago

    In reviewing my calculator app, I think adding support for keyboard inputs would make it more versatile and user-friendly. While the app currently works well with on-screen buttons, allowing users to input values directly from the keyboard will improve accessibility and overall usability. I plan to include this feature soon.

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

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

Oops! 😬

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

Log in with GitHub