bestelbus22@lemmy.world to Programmer Humor@programming.dev · 2 days agoFor that modern web feelinglemmy.worldimagemessage-square43fedilinkarrow-up1373
arrow-up1373imageFor that modern web feelinglemmy.worldbestelbus22@lemmy.world to Programmer Humor@programming.dev · 2 days agomessage-square43fedilink
minus-squaremikazuki@lemmy.worldlinkfedilinkarrow-up10·2 days 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-up14·2 days 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·1 day agoBut if the element itself already had an inline opacity value, that would be lost. 🙂
minus-squarebestelbus22@lemmy.worldOPlinkfedilinkarrow-up2·1 day agoYes very true, and also not likely at all ;)
minus-squareVictor@lemmy.worldlinkfedilinkarrow-up2·23 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 👍