bestelbus22@lemmy.world to Programmer Humor@programming.dev · 1 day agoFor that modern web feelinglemmy.worldimagemessage-square43fedilinkarrow-up1363arrow-down14
arrow-up1359arrow-down1imageFor that modern web feelinglemmy.worldbestelbus22@lemmy.world to Programmer Humor@programming.dev · 1 day agomessage-square43fedilink
minus-squaremikazuki@lemmy.worldlinkfedilinkarrow-up9·1 day agoDon’t just override opacity with null , it will override whatever the original style was. Before setting to 30% you need to store the original value and restore that in the timeout.
minus-squarebestelbus22@lemmy.worldOPlinkfedilinkarrow-up13·1 day agonull will actually default back to the rules coming from CSS, I use this all over the place as a pattern
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up2·16 hours agoBut if the element itself already had an inline opacity value, that would be lost. 🙂
minus-squarebestelbus22@lemmy.worldOPlinkfedilinkarrow-up2·12 hours agoYes very true, and also not likely at all ;)
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up2·10 hours agoNot in your code perhaps, which is a good thing 👍
Don’t just override opacity with null , it will override whatever the original style was. Before setting to 30% you need to store the original value and restore that in the timeout.
null will actually default back to the rules coming from CSS, I use this all over the place as a pattern
But if the element itself already had an inline opacity value, that would be lost. 🙂
Yes very true, and also not likely at all ;)
Not in your code perhaps, which is a good thing 👍