Wonderbear Comments - Answer Overflow

Most of the time it is no problem when it changes the layout imho. Even if your solution doesnt seem more complex to you, it is objectively definitely more complex than the solution with the padding

21 replies

KPCKevin Powell - Community

•Created by o_O on 6/1/2024 in #front-end

3 Cards 1 row where the center card is 1.5 times the size of the 1st and 3rd card.

I think its a bad idea using pseudo elements for major styles of the element

21 replies

KPCKevin Powell - Community

•Created by o_O on 6/1/2024 in #front-end

3 Cards 1 row where the center card is 1.5 times the size of the 1st and 3rd card.

@Chris Why not like this? https://jsfiddle.net/Lpondxw6/

21 replies

KPCKevin Powell - Community

•Created by o_O on 6/1/2024 in #front-end

3 Cards 1 row where the center card is 1.5 times the size of the 1st and 3rd card.

Why such a complex solution that is hard to read and understand?

21 replies

KPCKevin Powell - Community

•Created by Daniella on 5/21/2024 in #front-end

Do all Hamburger menus need Js?

There is also a solution with the :target selector

53 replies

KPCKevin Powell - Community

•Created by HaiderWaseem on 5/20/2024 in #front-end

Using createElement() outside the function

And this happens because you reference the exact same span element every time the addTask function is called. You have to create a new span element inside the function.

13 replies

KPCKevin Powell - Community

•Created by HaiderWaseem on 5/20/2024 in #front-end

Using createElement() outside the function

button.onclick=addTask(); Here you are not assigning the function to the onclick property, but instead you are calling the function and assigning the result which is undefined as you did not use a return statement.

13 replies

KPCKevin Powell - Community

•Created by HaiderWaseem on 5/20/2024 in #front-end

Using createElement() outside the function

Ah, I got it now. @HaiderWaseem First of all, you're using the onclick attribute which is dissaproved. And you're using it "wrong" anyway. See, the javascript inside the attribute will be immediately executed, causing the input to dissapear.

13 replies

KPCKevin Powell - Community

•Created by HaiderWaseem on 5/20/2024 in #front-end

Using createElement() outside the function

The fiddle is kinda broken. I cant even see the input element

13 replies

KPCKevin Powell - Community

•Created by KirK on 5/16/2024 in #front-end

Has anyone an idea what is happening here?

When asking such questions, also try to provide a minimal reproduction and leave everything out that is not mandatory for the error to happen.

10 replies

KPCKevin Powell - Community

•Created by KirK on 5/16/2024 in #front-end

Has anyone an idea what is happening here?

I found it out by minimizing your example. With this many lines of html and css, its hard to find the source of the error. I removed pretty much everything, except for the main, article and the first picture tag, as well as the belonging styles. Then I could search through the code much easier to find anything that might cause the issue.

10 replies

KPCKevin Powell - Community

•Created by KirK on 5/16/2024 in #front-end

Has anyone an idea what is happening here?

@KirK

10 replies

KPCKevin Powell - Community

•Created by KirK on 5/16/2024 in #front-end

Has anyone an idea what is happening here?

This property is experimental. Firefox is not affected because its not implemented there yet.

10 replies

KPCKevin Powell - Community