flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tianzhen Lin" <tang...@usa.net>
Subject RE: Testing ASDOC output
Date Mon, 07 Oct 2013 03:10:18 GMT
Anyways we can detect the Chrome exception and display instruction on how to
get around the issue?  Not until you posted the
--allow-file-access-from-files, I didn't know there is such a nifty trick.


-----Original Message-----
From: Maurice Amsellem [mailto:maurice.amsellem@systar.com] 
Sent: Sunday, October 06, 2013 6:34 AM
To: dev@flex.apache.org
Subject: Testing ASDOC output


This email describes a tip that people working on flex asdoc might find

I generated the asdoc for flex-sdk to make sure everything was fine after
"include-examples" changes.
Then noticed links to Properties, Methods, Examples in the title bar didn't
show, whereas they are showing correctly on http://flex.apache.org/asdoc/

Did I break something?
After digging in the history of changes, xslt, js, java, setting traces and
alert boxes, and scratching my head for a while, I finally figured out:

Chrome does not allow inner frame to access outer frame props, when running
on local disk.

IE and Firefox do not have this issue.

To work around it, start chrome.exe with --allow-file-access-from-files



View raw message