Issue
First of all, sorry for not providing the ALL the needed code. Let me explain the reason and it's not simply because of private info and codes... the project is really extensive and all coded by hand without any framework, so the only way to perfectly reproduce the exactly same situation would be having the whole project, so my words are the only reference.
Ok... let's get going...
I have a Stylesheet that changes all buttons:
button{
font-family: 'autobus';
font-size: 15px;
background: rgb(8,77,110);
border: 1px solid rgb(231,235,245);
color: rgb(231,235,245);
border-radius: 3px;
cursor: pointer;
}
And a few others that changes really specific buttons:
.innerForm > button {
margin-top: -25px;
margin-right: -25px;
float: right;
font-size: 30px;
border: none;
background: none;
cursor: pointer;
}
After developing a part of my system where I can add some elements containing input and buttons through some input and buttons I realized that something really was with an unexpected behavior...

(source: fbcdn.net)
As you can see, only on the newly javascript added "input+button" the button respects the CSS... I realized only after adding the elements that the ones coming already build from the server were with different styling because I'd liked them without the background... anyway both are exactly the same in the browser html as you can see:

(source: fbcdn.net)
No classes... only one onclick attribute to call the javascript function to remove the item. All the others "specific buttons stylizing" have the
cursor: pointer;
While these backgroundless buttons doesn't even changes the cursor appearance...
If it wasn't a really messy one I wouldn't even bother myself on coming to ask here.
Any other needed info, just comment and I can edit adding it.
So... anyone has ever seen something like that?
PS: If someone answer why the javascript added item doesn't show on HTML it's "value='21/12/2019'" and still shows it on the visual interface, I'll upvote too for the explaination. And in case the main question doesn't acquire a proper answer, I'll vote this "value issue" explanation as the answer if someone answer correctly.
Solution
As you can see at the HTML image, "buttoM" was misspelled. The correct would be "button". This changing fixed the issue.

(source: fbcdn.net)
Answered By - Gilkan Solizaris
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.