Thanks for the clarification, and for your fixes Harbs,
I will make the other changes to add the import to cover js build scope for
ApplicationBase and the two layout beads today.
On Tue, Jul 11, 2017 at 4:40 AM, Josh Tynjala wrote:
> That sounds reasonable.
>
> - Josh
>
> On Mon, Jul 10, 201
That sounds reasonable.
- Josh
On Mon, Jul 10, 2017 at 9:32 AM, Alex Harui
wrote:
> Well, the goal is to not have the framework code use the native Event.
> Maybe we should add a warning that we can turn on for our code but is off
> by default.
>
> -Alex
>
> On 7/10/17, 8:52 AM, "Josh Tynjala"
Well, the goal is to not have the framework code use the native Event.
Maybe we should add a warning that we can turn on for our code but is off
by default.
-Alex
On 7/10/17, 8:52 AM, "Josh Tynjala" wrote:
>This behavior is because the native HTML classes aren't in a package. The
>compiler trea
This behavior is because the native HTML classes aren't in a package. The
compiler treats everything that's not in a package the same as classes like
Number, Boolean, and String, which you don't need to import.
It seems potentially tricky to change this behavior, unless you have a
whitelist. You w
Yes, good catch.
I'm wondering if the compiler should not auto-import native HTML classes.
-Alex
On 7/10/17, 1:16 AM, "Harbs" wrote:
>Good catch.
>
>Without looking at them, I’d guess that they are bugs. Clipboard was my
>error and I just committed a fix for that.
>
>Thanks,
>Harbs
>
>> On Jul
Understand! :)
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Question-about-Events-possible-bugs-tp63023p63031.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
gt;
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context:
> http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Question-about-Events-possible-bugs-tp63023p63025.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
GraphicContainer was another one I was involved in, so I know that’s an
omission as well. (committed)
> On Jul 10, 2017, at 11:16 AM, Harbs wrote:
>
> Good catch.
>
> Without looking at them, I’d guess that they are bugs. Clipboard was my error
> and I just committed a fix for that.
>
> Than
Harbs,
I think this import could be outside COMPILE::JS.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Question-about-Events-possible-bugs-tp63023p63025.html
Sent from the Apache Flex
Good catch.
Without looking at them, I’d guess that they are bugs. Clipboard was my error
and I just committed a fix for that.
Thanks,
Harbs
> On Jul 10, 2017, at 11:06 AM, Greg Dove wrote:
>
> I noticed a problem with VerticalFlexLayout in IE11 (and presumably older
> IE browsers).
>
> The
I noticed a problem with VerticalFlexLayout in IE11 (and presumably older
IE browsers).
The JS output causing problems has
child.dispatchEvent(new Event("layoutNeeded"));
The reason is that the org.apache.flex.events.Event import is missing from
the
COMPILE::JS build scope
So it is falling back
11 matches
Mail list logo