Boss: Logo needs to be more grey. Touch it up in photoshop.

Me: .logo {opacity: 0.6;}

Boss: perfect!

Client not paying?

Instead of reducing opacity, add FartScroll until they pay!

Theonion.github.io/fartscroll.js

❎ Client not paid?
✅ Add opacity to the body tag and increase it every day until their site completely fades away

"Make it a bit more darker"
Me - "Okay"
"Ummm..a bit more lighter? Sorry, this is such a minor change,I figured it wouldn't need any documentation"
Me - "It's alright"
"Could you please make this text small, and reduce the opacity to 70%"
Me - *Rise in the levels of mental irritation, body's and blood's temperature*
"Oh and don't forget to add some tint to the background"
"Hey, sorry I forgot. We need to add another text below this image."
Me - Oh man oh man

Probably the most useful answer in stackoverflow (atleast for me)

When designers use screen to give images transparency and set black text to 80% opacity instead of making it gray 🙂🔫

cssRant

Why for the sake of world peace can't Edge inherit "opacity" to children?
This drives me insane!!!11!!one!eleven!!1!!

Get you fucking turds together dear browser developers!

The whole webDev business gets serious crippling depression from your brainless way of pooping out what you call "browser"!

I am sad, I am not getting paid for last month's work as it was some "mis-communication" and my contract was available till August! 2 options

> set opacity of the website in such a manner it partially shows anything
> set the website on fire

So apparently Firefox can't handle (quick) animations from opacity 0 to opacity greater-than-zero and glitches around. Instead you need to animate starting from something greater than 0, like 0.001.

I had to debug this shit and it just adds to my reasons to dislike this browser.

> be me
> be developing a react native app
>realize the iPhone X notch is clipping your content on the first/home screen of the app
>google says: simple fix
>find a built-in react native thing to add safe area padding
> refresh the app
> ohno.png
> the other screens with navigation bars already have built in padding
> TOOMUCHPADDING.jpeg
> remove safe area thingy
> finds a clever, not particularly hacky way to pad the home screen without showing the header bar by setting its height to 0 and the color to match the content background
> more-problems.app
> there’s a small 1–pixel light colored line separating the header from the content clearly breaking the otherwise continuous single color background
> google.sh
> wtf.txt
> stackoverflow.html
> no responses except something I’d already done
> keep experimenting
> tries basically everything to figure out where that line is coming from
>sets borders to thicccc and bright red
>no bottom border? Ok that’s not it
>opacity?
>forgetaboutit.mov
>try shifting the header position around by a few pixels? Maybe it’s misaligned with the white parent layer underneath?
> nope.jpg
>it’s past bedtime
>Sleep.jpg
>thenextday(today).zip
> what about the content? Is that misaligned?
> nope2.jpg
>Maybe its an iOS feature not a react thing?
> make a test Xcode project, completely native to test
> negative.dng (pun intended)
> more-furious-googling.mp3
> find a native iOS stackOverflow question with the same issue (1px line)
> realize your Xcode test wasn’t done properly.
>atleastimmakingprogress.iso
> start looking into the SO post
>it’s native so I have to find out how to do it in react-native
>invent a bunch of style parameters that don’t exist in the documentation to see if there’s an undocumented thing
>loadsaloadsaerrors.log
>googles for a react native version of the iOS only SO post
> somethingpromising.tar.gz
> *tries it*
> “Haha nope” -my code
> whataboutthisotherthing.bin
> KENSISHSBUCNEGWISBVSIDNRVSIDNFIRJRBDKFNFIDJFIFKFNR
> HOLY FUCK
> IT WORKED
> AFTER TWO FUCKING DAYS OF SHITTERY AND SHENANIGANS
>AND MANY STACKOVERFLOW EDITS TO A NOW VERY MESSY POST
>THEREISNOMOREBORDER(final).zip
>*screams of relief*

Omfgggggggggggggggggggg
Fuck you typescript.

A whole day wasted working on react native pull to refresh bug, wondering why the fucking hell shit doesn't even appear when u try to pull. And so many other weird shit like touchable opacity not showing up.

Guess what was the problem? Fucking typescript importing shit from react-native-gesture-handler.

Btw I live and breathe typescript. I appreciate typescript everyday but for today fuck you typescript.

Why are you all so obsessed with hating jQuery? For me it just does the job done. Animate stuff. But I agree being totally dependant on javascript is bad for any website. Seen hundreds of wordpress spaghetti code where fancy effects were made with jquery like CSS opacity 0 and jquery animate to 1... What a bullshit. But yeah I still love jquery. Easy, fast and reliable.

Laziest habit? Anything done between 1pm-4:30pm and 4:59pm-8pm. During that time, habits include unnecessary refactoring, poking the CI/CD containers, editing already made prototypes in gimp inkscape, pasting stackoverflow topics to youtube, bouncing from macOS, windows and kde distros in search of zen/rice, adding a calendar emoji on my slack :), making useless automation scripts, building on every variable's value change, tinkering pixels, shades, gradients (and their angles), dimens, anim values, anim curves, opacity, blurs and just nuking the ui just to copy paste an old one, 60% just chatting in code alongs, changing key bindings (from ide to OS), and ultimately zoning out on a podcast about cyber security. And of course: waiting for ++ and comments

rgba(0,0,0,0.5)
#0008
Or
#000 opacity: .5

Finally got to the point where the title transition goes to 0 opacity in both elements

When - webkit-background-clip does not work with any kind of transition or animation and you're forced to make duplicate div on top of original without it and opacity:0. Just because designer want's quick fade transition.

when the designer doesn't know that opacity style affects the whole element and everything within it... why don't you just give me the exact color and color scheme?

I came up with a new css fuckemup🤪

*:after{
contents:'meh';
opacity:0.2;
}

I want some help with media queries I am new and learning so please don't bash me up :

Here is my css code I want to know how to solve the issue :

/* About Section */

.about
{
height:600px;
padding:50px;
display: flex;
flex-direction: row;
justify-content: space-between;
align-items: center;
}

.abouttext
{
 position: relative;
 padding: 0 50px;
 height: inherit;
}

.abouttext h1
{
position: relative;
left: 230px;
}

.abouttext img{
width:20vw;
position: absolute;
top:50px;
}

.aboutlist
{
width:50%;
}

ol
{
list-style: none;
color: #e0501b;
}

ol li
{
font-size: 34px;
position: relative;
margin-bottom: 20px;
}

li p
{
font-size:16px;
color:#000;
padding-left:60px;
line-height:30px;
opacity:0.6;
}

li span
{
float: right;
  position: absolute;
 line-height: 25px;
 font-weight: 600;
}