earp

5 ms·

1.
by earp 11y ago
There's one right now where a combination of flex and transform3d will cause things to simply disappear in Chrome and Safari but I haven't searched for any issues reported on that. The problem is progressively getting worse, so I&
2.
by earp 11y ago
Well, I made some code that would emulate flexbox in IE for a specific HTML structure (it would parse classnames in the HTML and not the CSS, the code is still around on https://github.com/wiredearp/spiritual-mix/b
3.
by earp 11y ago
Flex was working out a lot better for me some ten years ago, in Mozilla extensions, as it was. There's just too many rendering glitches and performance problems with flex nowadays, so I've moved on to scripted layout. I just felt
4.
by earp 12y ago
This is like watching a nuclear superpower go down in a fist fight. I honestly think HTML5 was designed to eliminate Mozilla.
5.
by earp 12y ago
We didn't like how attributes worked, so we changed it, but then people were using it and now we have to change it back. It's not a particularly good point. I would like to know more about the fundamental problem with existing spe
6.
by earp 12y ago
Good info. With no specification to back it up, I might go back to my hand-rolled gestures-style library. I retired it because of imminent standardization, but at this point, it seems as likely to be standardized as everything else. I promi
7.
by earp 12y ago
That's the CSS property already being used. The controversial specification is at https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEve...
8.
by earp 12y ago
I wonder what will happen with the Polymer polyfills for WebComponents, a technology that Safari also hasn't declared intent to implement. And then I wonder what will happen with the polyfill for PointerEvents that already comes bund