Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

2014 CSS Report: Examining how CSS is being used in the wild

reports.quickleft.com

Post reply on HN
Print view View original

1–10 of 24 posts

Re: 2014 CSS Report: Examining how CSS is being used in the wild

#2

Post by mrdrozdov »

Highest z-index was an astonishing 999999999999999999999999999 or 9.99e26. With a default key repeat on OS X, this would take 3 seconds of holding down 9 to type. If you took that many pieces of paper at .05mm thick, the stack would reach from Earth to the Sun 10 trillion times. The worst part about this large of a z-index is that a number that high will overflow and not work in the expected manner anyhow. The lowest was a more reasonable -999999.​

FWIW, ​max z-index that is cross-browser safe is: 16777271

Re: 2014 CSS Report: Examining how CSS is being used in the wild

#3

Post by leeoniya »

imo, flex-box and evangelism of box-sizing border-box have been the best things since CSS3 selectors and transforms/transitions.

i only wish that elements could propagate style rules as if they were parents of all the related td/th cells. there's still no way to specify text-align and font-* on entire columns easily, which is just silly.

Re: 2014 CSS Report: Examining how CSS is being used in the wild

#6

Post by freshyill »

mrdrozdov wrote: post #2

Highest z-index was an astonishing 999999999999999999999999999 or 9.99e26. With a default key repeat on OS X, this would take 3 seconds of holding down 9 to type. If you took that many pieces of paper at .05mm thick, the stack would reach from Earth to the Sun 10 trillion times. The worst part about this large of a z-index is that a number that high will overflow and not work in the expected manner anyhow. The lowest…

I think we've all been there and started throwing out crazy z-index values at one point or another, usually out of frustration. The only real solution is to keep this stuff under control from the start and always use exactly the z-index you need.

Re: 2014 CSS Report: Examining how CSS is being used in the wild

#7

Post by jszymborski »

freshyill wrote: post #6
mrdrozdov wrote: post #2

Highest z-index was an astonishing 999999999999999999999999999 or 9.99e26. With a default key repeat on OS X, this would take 3 seconds of holding down 9 to type. If you took that many pieces of paper at .05mm thick, the stack would reach from Earth to the Sun 10 trillion times. The worst part about this large of a z-index is that a number that high will overflow and not work in the expected manner anyhow. The lowest…

I think we've all been there and started throwing out crazy z-index values at one point or another, usually out of frustration. The only real solution is to keep this stuff under control from the start and always use exactly the z-index you need.

Ahaha totally. I can just imagine the hilarious scene where a poor dev just breaks after a solid 45 minutues of trying to get that god-forsaken div to overlap another and gets to his feet, punchs down the 9 key for a whole 3 seconds screaming a 3-syllable combination of rage-soaked curses ("cock-sucking cunt" comes to mind), finally collapsing back into his seat on the last; too pissed to even bother hitting Ctrl+R to see if it had worked, typing 'git add . && git commit -m "fuck everything." ' before going home.

Re: 2014 CSS Report: Examining how CSS is being used in the wild

#8

Post by razwall »

freshyill wrote: post #6
mrdrozdov wrote: post #2

Highest z-index was an astonishing 999999999999999999999999999 or 9.99e26. With a default key repeat on OS X, this would take 3 seconds of holding down 9 to type. If you took that many pieces of paper at .05mm thick, the stack would reach from Earth to the Sun 10 trillion times. The worst part about this large of a z-index is that a number that high will overflow and not work in the expected manner anyhow. The lowest…

I think we've all been there and started throwing out crazy z-index values at one point or another, usually out of frustration. The only real solution is to keep this stuff under control from the start and always use exactly the z-index you need.

First step is for people to understand stacking contexts (https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Under...). Blew my mind after years of web development to learn that I had really had no idea how z-index worked.

Re: 2014 CSS Report: Examining how CSS is being used in the wild

#9

Post by WhitneyLand »

I wish Apple would add a SASS/CSS compiler into XCode for native UI. I know there are a couple side projects for this but if it were baked in it could really take off.

Besides the potential of sharing across platforms, it would be one less system for layout and styles that had to be learned.

Post reply on HN