Thanks Alex for this advice. Sorry for my delayed reply.

I created an issue in the JIRA for a better documentation.

https://issues.apache.org/jira/browse/FLEX-33432

I hope we / Google can fix this.

Thanks

Marcus

Am 17.03.2013 um 04:40 schrieb Alex Harui <[email protected]>:

> Flex apps are generally two-frame SWFs.  It occurred to me that maybe the
> issue is that the Flex app is not seeing what it expects from Pepper Flash
> in order to advance to the second frame.
> 
> You could try a custom preloader that reports the information that
> mx.preloaders.Preloader is looking for, specifically this expression:
> 
> ((loaded >= total && total > 0) || (total == 0 && loaded > 0) || (root is
> MovieClip && (MovieClip(root).totalFrames > 2) &&
> (MovieClip(root).framesLoaded >= 2)) ))
> 
> Where loaded is loaderInfo.bytesLoaded and total is loaderInfo.bytesTotal
> 
> What version of Flex are you using?  If you are using Adobe Flex, try
> turning off RSLs and see if that makes a difference.
> 
> On 3/16/13 2:58 PM, "Marcus Fritze" <[email protected]> wrote:
> 
>> Thank you Alex.
>> 
>> This is very strange. Ok I have tested this issue the whole day now.
>> 
>>> Does it work if you run your app from localhost or a server?  Maybe Chrome
>>> has different security requirements for local content.
>> 
>> Ok I realized that both locations (localhost and server) are not working. But
>> other Flex applications are working.
>> 
>>> Are you on Mac or Win?  Maybe I'll find some time to try it myself.
>> 
>> Mac 10.8.3
>> 
>> Ok something is really strange. The Chrome Version 25.0.1364.172 with
>> 11.6.602.180 Pepper Flash Player is working now. This didn't worked some 
>> hours
>> ago, but now it's working. And I didn't changed anything.
>> 
>> But the Chrome Version 27.0.1423.0 dev with 11.6.602.171 Pepper Flash Player
>> is still not working.
>> 
>> As I already mentioned in my previous mails, the page loads and I see the
>> correct backgroundColor of my application, but the content is missing.
>> 
>> Ok another interesting thing: the right mouse-click menu has the same
>> menu-items as when a working application is loading.
>> 
>> Right mouse-click menu-items of a working Flex application (when application
>> is completely loaded):
>> -> Print
>> -> Separator line
>> -> Settings...
>> -> Global Settings...
>> -> About Flash Player 11.6.602.171...
>> 
>> Right mouse-click menu-items of a NOT working Flex application Chrome OR a
>> working Flex application when loading:
>> -> Zoom in
>> -> Zoom out
>> -> Show all
>> -> Separator line
>> -> Quality (with sub menu)
>> -> Play
>> -> Loop
>> -> Separator line
>> -> Rewind
>> -> Forward
>> -> Back
>> -> Separator line
>> -> Print
>> -> Separator line
>> -> Settings...
>> -> Global Settings...
>> -> About Flash Player 11.6.602.171...
>> 
>> Another note: because I don't have a Pepper Flash Debug version, I trace an
>> output to MonsterDebugger in the creationComplete function of my application.
>> But when running the application in Chrome, nothing happens in
>> MonsterDebugger.
>> 
>> It seems that the application is not be completely loaded in Chrome.
>> 
>> I don't know how to debug or get further informations about this issue. I 
>> have
>> found chrome://tracing/ to trace something in Chrome, but I don't have any
>> idea where I can see anything related to my app in this trace.
>> 
>> Thanks
>> 
>> Marcus
>> 
>>> 
>>> On 3/16/13 8:23 AM, "Marcus Fritze" <[email protected]> wrote:
>>> 
>>>> Ok, I debuged in Firefox and doPhasedInstantiation gets only called 3 times
>>>> in
>>>> my application (when application is loading).
>>>> 
>>>> 
>>>> Am 16.03.2013 um 15:51 schrieb Alex Harui <[email protected]>:
>>>> 
>>>>> First, make sure it isn't the app.  Sometimes subtle differences in 
>>>>> browser
>>>>> window sizes cause Spark apps with multiline text to get into an
>>>>> invalidation loop.  Put a breakpoint on doPhasedInstantiation and see if 
>>>>> it
>>>>> never stops getting called.  Well-behaved apps might see it get called a
>>>>> dozen times but then it should stop if the app is idle.
>>>>> 
>>>>> 
>>>>> On 3/16/13 7:09 AM, "Marcus Fritze" <[email protected]> wrote:
>>>>> 
>>>>>> Hi list,
>>>>>> 
>>>>>> sorry for this off-topic question but I am almost crying, because nothing
>>>>>> is
>>>>>> working, as it should!!!
>>>>>> 
>>>>>> Ok, I experienced a bug when uploading files in Chrome using
>>>>>> FileReference.upload() and wanted to test this bug. (later in another
>>>>>> email
>>>>>> some word to this bug) So I created a Flex project and opened this 
>>>>>> locally
>>>>>> saved project in Chrome with the URL
>>>>>> 
>>>>>> file:///Users/marcus/Documents/workspace/FileUploadBug/bin/FileUploadBugTe
>>>>>> st
>>>>>> .h
>>>>>> tml
>>>>>> 
>>>>>> But all I can see is a blank white page (the backgroundColor of my
>>>>>> application). When I change the backgroundColor in the project, Chrome
>>>>>> shows
>>>>>> me the new backGroundColor, but the rest (the whole application) is
>>>>>> missing!
>>>>>> I
>>>>>> have tested other flex projects I have created and the same issue!
>>>>>> 
>>>>>> In Firefox everything is working fine.
>>>>>> 
>>>>>> My system:
>>>>>> 
>>>>>> Mac OS X 10.8.3 (today I updated to the new version!)
>>>>>> German OS X language
>>>>>> 
>>>>>> Chrome Version 27.0.1423.0 dev with 11.6.602.171 Pepper Flash Player
>>>>>> and
>>>>>> Chrome Version 25.0.1364.172 with 11.6.602.180 Pepper Flash Player
>>>>>> 
>>>>>> both are not working.
>>>>>> 
>>>>>> Can someone please confirm!!!
>>>>>> 
>>>>>> I would create a bug in the chrome issue management system, if someone 
>>>>>> can
>>>>>> confirm this issue!
>>>>>> 
>>>>>> Thanks in advance.
>>>>>> 
>>>>>> Marcus Fritze
>>>>> 
>>>>> -- 
>>>>> 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
>>> 
>> 
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
> 

Reply via email to