Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates
 64.18.1.189 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "users@flex.apache.org" <users@flex.apache.org>
Date: Sat, 16 Mar 2013 20:40:39 -0700
Subject: Re: [OT] open locally saved Flex projects in Chrome browser, not
 working anymore?
Thread-Topic: [OT] open locally saved Flex projects in Chrome browser, not
 working anymore?
Thread-Index: Ac4ikWi5LGi/dE8YQfKdc2TOoHs5JgAL8kXd
Message-ID: <CD6A8948.4F4E9%aharui@adobe.com>
In-Reply-To: <56D31873-C679-4AEA-87B1-56D76BE7486D@googlemail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.15.0.121009
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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 >=3D total && total > 0) || (total =3D=3D 0 && loaded > 0) || (roo=
t is
MovieClip && (MovieClip(root).totalFrames > 2) &&
(MovieClip(root).framesLoaded >=3D 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" <marcus.fritze@googlemail.com> wrote:

> Thank you Alex.
>=20
> This is very strange. Ok I have tested this issue the whole day now.
>=20
>>  Does it work if you run your app from localhost or a server?  Maybe Chr=
ome
>> has different security requirements for local content.
>=20
> Ok I realized that both locations (localhost and server) are not working.=
 But
> other Flex applications are working.
>=20
>> Are you on Mac or Win?  Maybe I'll find some time to try it myself.
>=20
> Mac 10.8.3
>=20
> 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.
>=20
> But the Chrome Version 27.0.1423.0 dev with 11.6.602.171 Pepper Flash Pla=
yer
> is still not working.
>=20
> 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.
>=20
> Ok another interesting thing: the right mouse-click menu has the same
> menu-items as when a working application is loading.
>=20
> Right mouse-click menu-items of a working Flex application (when applicat=
ion
> is completely loaded):
> -> Print
> -> Separator line
> -> Settings...
> -> Global Settings...
> -> About Flash Player 11.6.602.171...
>=20
> 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...
>=20
> Another note: because I don't have a Pepper Flash Debug version, I trace =
an
> output to MonsterDebugger in the creationComplete function of my applicat=
ion.
> But when running the application in Chrome, nothing happens in
> MonsterDebugger.
>=20
> It seems that the application is not be completely loaded in Chrome.
>=20
> 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 an=
y
> idea where I can see anything related to my app in this trace.
>=20
> Thanks
>=20
> Marcus
>=20
>>=20
>> On 3/16/13 8:23 AM, "Marcus Fritze" <marcus.fritze@googlemail.com> wrote=
:
>>=20
>>> Ok, I debuged in Firefox and doPhasedInstantiation gets only called 3 t=
imes
>>> in
>>> my application (when application is loading).
>>>=20
>>>=20
>>> Am 16.03.2013 um 15:51 schrieb Alex Harui <aharui@adobe.com>:
>>>=20
>>>> First, make sure it isn't the app.  Sometimes subtle differences in br=
owser
>>>> 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.
>>>>=20
>>>>=20
>>>> On 3/16/13 7:09 AM, "Marcus Fritze" <marcus.fritze@googlemail.com> wro=
te:
>>>>=20
>>>>> Hi list,
>>>>>=20
>>>>> sorry for this off-topic question but I am almost crying, because not=
hing
>>>>> is
>>>>> working, as it should!!!
>>>>>=20
>>>>> 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 lo=
cally
>>>>> saved project in Chrome with the URL
>>>>>=20
>>>>> file:///Users/marcus/Documents/workspace/FileUploadBug/bin/FileUpload=
BugTe
>>>>> st
>>>>> .h
>>>>> tml
>>>>>=20
>>>>> But all I can see is a blank white page (the backgroundColor of my
>>>>> application). When I change the backgroundColor in the project, Chrom=
e
>>>>> 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!
>>>>>=20
>>>>> In Firefox everything is working fine.
>>>>>=20
>>>>> My system:
>>>>>=20
>>>>> Mac OS X 10.8.3 (today I updated to the new version!)
>>>>> German OS X language
>>>>>=20
>>>>> 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
>>>>>=20
>>>>> both are not working.
>>>>>=20
>>>>> Can someone please confirm!!!
>>>>>=20
>>>>> I would create a bug in the chrome issue management system, if someon=
e can
>>>>> confirm this issue!
>>>>>=20
>>>>> Thanks in advance.
>>>>>=20
>>>>> Marcus Fritze
>>>>=20
>>>> --=20
>>>> Alex Harui
>>>> Flex SDK Team
>>>> Adobe Systems, Inc.
>>>> http://blogs.adobe.com/aharui
>>>>=20
>>>=20
>>=20
>> --=20
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>=20
>=20

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui