In the pre-elastic scrolling world, hiding something above zero was a safe bet. These days… not so much.pic.twitter.com/Xj53NneQ6m
-
Show this thread
-
I just hid a little easter egg on my site. But I could only get it to work in Chrome (with position: fixed). https://aresluna.org/
3 replies 0 retweets 7 likesShow this thread -
I found a new way which works on Safari, too. “position: absolute” with a transform in 3D space. Scroll up for an easter egg! http://aresluna.org pic.twitter.com/WmWPasaWL8
3 replies 0 retweets 10 likesShow this thread -
Twitter or the web is home to more weird, messy interactions. Here’s another one. I’m not moving my cursor at all.pic.twitter.com/GZvwgDIRdS
6 replies 1 retweet 7 likesShow this thread -
Replying to @mwichary
And this is why the CSS working group is now strongly against any new features that could create similar feedback loops (current state triggers a style change that changes the state, causing the style to turn off, reversing the state change…) So many nice things we can't have…
2 replies 0 retweets 2 likes -
Replying to @AmeliasBrain
Seems like those would be possible to detect and stop when they happen?
1 reply 0 retweets 0 likes -
Replying to @mwichary
And you're certainly not the first one to suggest that. I think the issue is compound complexity making it harder to detect feedback loops.
1 reply 0 retweets 1 like
I always wondered whether it was possible for :hover stuff to never reflow anything by default – and you just needing to intentionally enable reflow. But maybe that doesn’t solve anything. (Although something to “freeze the layout” would be generally handy in CSS.)
-
-
Replying to @mwichary
The CSS Containment proposal addresses a bit of this. You can declare an element to "contain" all its paint or layout so that its children can't create side effects outside the container. https://drafts.csswg.org/css-contain-1/ But probably too late to change default for :hover!
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.