Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

All solutions

  • Submitted


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

    Any advice, feedback, suggestion I would appreciate.

  • Submitted


    What are you most proud of, and what would you do differently next time?

    • For first time ever using js in practice.
    • Next time, hopefully, I'll try to make better decisions and make things faster.

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

    • Made text smaller than browser allowed me to with font-size via transform: scale(). This has been a problem for most of my challenges, but I haven't done anything to solve it, but here I am.

    • Some struggle with js took place, but I overcame just by thinking more time than I should have for the solution.

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

    Animation from display: block; to display:none; that would work in every browser. (My works neither.)

  • Submitted


    What are you most proud of, and what would you do differently next time?

    By getting knowledge that :hover pseudo-element can't apply any changes to parent of the selected element .

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

    1.I've tried to make change my #blog-preview-card's(parent element, container) shadow-box value by hovering the #header(child element) .This turned out to work only in opposite way, e.g. this way:

    .parent:hover .child { background-color: white; }. (When you hover over the parent element, it will change the background color of the child element to white)

    I've seen some variants for solution of my problem with pseudo-element :has and assigning position: relative to parent and position: absolute to child element but it didn't worked at my case. If It's possible and can work with my code please write your options. I struggled a lot with this and it's a bit annoying to leave it how it is, but if it's realm of JavaScript usage, okay, so be it.

    2.W3C validator, seems, not to be complaining about my code, but if you look and it's semantic will seem to you wrong/unnecessary/unreasonably overcomplicated, I'll be grateful for letting me know.