You're right it works much better in Chrome. I guess later webkit must be
able to resolve "new CustomEvent" to "new
org.apache.flex.events.CustomEvent", and the HTTP DOM lets you dispatch
something other than DOMEvent.
I would think we need to support older webkit versions, though, so that
brings us back to FlexGlobals or replacing the whole event system.
On 3/31/13 7:39 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> Chrome (if it's up to date) should have the same webkit version as my
> Safari 6 (I think), so if it's a version "problem", this should show
> you in Chrome what I see in my Safari (and Chrome and Firefox, both on
> OS X and WinXP/7).
>
> EdB
>
>
>
> On Sun, Mar 31, 2013 at 4:33 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:
>> My Safari is 6.0.3, the current version on OS X 10.8.3. I'm curious to
>> hear how the app is functioning for you in Chrome?
>>
>> EdB
>>
>>
>>
>> On Sun, Mar 31, 2013 at 4:28 PM, Alex Harui <aha...@adobe.com> wrote:
>>>
>>>
>>>
>>> On 3/31/13 7:03 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>>>
>>>> On selection from the dropdownlist it hits the breakpoint. Stepping
>>>> into brings me to UIBase::dispatchEvent, where the only argument is a
>>>> CustomEvent (so that was created properly, it seems) and then it
>>>> enters the whole event chain that lead to the value of the
>>>> dropdownlist being displayed in the textarea next to it.
>>>>
>>>> Is there a "goog.require('org.apache.flex.events.CustomEvent')" in
>>>> your MyInitialView.js?
>>> This is very strange. Yes, I have the require for CustomEvent, but the code
>>> "new CustomEvent()" throws that reference error because it, from my
>>> understanding of JS, should not resolve. At minimum, I think the code
>>> should be "new org.apache.flex.events.CustomEvent".
>>>
>>> I'm on Mac Safari 5.1.7. Are you on some newer version that resolves
>>> functions/constructors more intelligently?
>>>
>>>>
>>>> EdB
>>>>
>>>>
>>>> On Sun, Mar 31, 2013 at 3:50 PM, Alex Harui <aha...@adobe.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On 3/31/13 6:33 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>>>>>
>>>>>> In Safari, with the "error console" opened, I get the following
>>>>>> "warning/message" (not an exception, as far as I can tell):
>>>>>>
>>>>>> event.layerX and event.layerY are broken and deprecated in WebKit.
>>>>>> They will be removed from the engine in the near future.
>>>>>>
>>>>>> Is that what you are seeing as well? Or do you get another message?
>>>>>>
>>>>> No, haven't seen that. You are right that the timer buttons work, but
>>>>> Transfer doesn't and OK doesn't.
>>>>>
>>>>> Try this:
>>>>> Set a breakpoint on MyInitialView.js on line 213 where it says "var self =
>>>>> this = value". The entire function starts on line 211 for me and looks
>>>>> like
>>>>> this:
>>>>>
>>>>> MyInitialView.prototype.$EH1 = function(event)
>>>>> {
>>>>> var self = this;
>>>>> this.dispatchEvent(new CustomEvent('listChanged'));
>>>>> };
>>>>>
>>>>> Pick from the dropdownlist and it should hit the breakpoint. Now try to
>>>>> step into the CustomEvent constructor. For me, it doesn't go in and after
>>>>> it stops running code, the console shows: "Reference Error: Can't find
>>>>> variable: CustomEvent".
>>>>>
>>>>> What happens for you?
>>>>>
>>>>> --
>>>>> Alex Harui
>>>>> Flex SDK Team
>>>>> Adobe Systems, Inc.
>>>>> http://blogs.adobe.com/aharui
>>>>>
>>>>
>>>>
>>>
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
