I agree that we shouldn't make Math.ceil the default code path. What does
the change look like? Could it be post-processed onto the JS output when
somebody needs it? I didn't think Opera was one of our target browsers.
-Alex
On 8/20/17, 1:23 AM, "Harbs" wrote:
>I discovered a bug in Blink (C
Bonjour,
En congés jusqu'au 4 septembre, je prendrais connaissance de votre message à
mon retour.
Cordialement,
Vincent/AFTER24
I don’t think the loops are so complex, but who knows.
I’m getting 6 of these kinds of errors. One is in one place in the code flow
and the other 5 are all in a second place.
I can live with this until you have the time. It compiles the code, but it’s
quite large and not minified.
Harbs
> On
A quick look at the GCC code indicates that you are hitting a limit in
their control-flow analysis. They had a constant as a gate to detect
infinite loops in the control flow. It is possible that there may be a
loop in the generated JS or that your app is just too complicated and that
constant sh
Since updating to the newest changes to Falcon, I started getting some errors
that look like this:
Aug 20, 2017 6:28:02 PM com.google.javascript.jscomp.LoggerErrorManager println
SEVERE:
/Users/harbs/Documents/git/PrintUI/printui-flexjs/PortedPrintUI/bin/js-debug/com/printui/model/vos/StoryVO.js
I discovered a bug in Blink (Chrome and Opera).[1]
The workaround for this is to set the width and height of svg elements to round
numbers (using Math.ceil seems to generally be a good way of doing this). I
have implemented the workaround in my app and it works well. I’m debating on
whether thi
