Richard Herrera
Richard Herrera
@ilanbiala Everything I've done is available in this repository. Also, guys, there is simply not enough demand to polyfill this feature into older browsers. Flexbox came at about the same...
Maybe. Hold tight, I've got a fresh testbed coming your way in a few minutes. This one tests more cross/main sizing , floats, overflows, etc. Needless to say, many more...
I can't tell if the differences in overflow visible/hidden are intentional or a bug. Re: `/comprehensive`, IE10's flexbox model behaves exactly like Chrome. So they're definitely following some sort of...
Still trying to debug it, but I was using 0.4.0-pre1. I'll try the update.
Ok, a bit more info: I have a browserify module with the following requires: ``` js // Ractive var Ractive = require("ractive"); require("ractive-transitions-fade"); require("ractive-transitions-slide"); console.log(Ractive.transitions); ``` On the browser, the...
Yup. I took a minute to strip the testbed down to the minimum. I have it down to four files. The following sample still generates the warning and does not...
Progress! In the example, the warning goes away and the transition applies if I replace: ``` js var Ractive = require("ractive"); ``` With: ``` js var Ractive = require("Ractive/build/Ractive.runtime.js"); ```...
Sorry, I'm a little confused. Are you trying to use the proxy with FF3, or is FF3 choking on this code regardless?
Two options here: 1. Go this route, patch FF3 bug. 2. Take care of this and further incompatibilities by wrapping respond.js in an IE conditional. @scottjehl, @paulirish, any reason not...