[Sugar-devel] [sugar-web] do webkit frames run on different threads?

[Code Raguet]

>
> We should not set window.top.sugar = {} from the javascript side. Instead
> we should if isStandalone callback({}).

yes, we are on it


My point in this thread is:

*should we develop thread-safe code when handling window.top props???*

chrome: not mandatory
opera: yes, we should
webkit:   ??????????




On Thu, Dec 19, 2013 at 11:08 PM, Rogelio Mita <
rogeliomita at activitycentral.com> wrote:

>
> 2013/12/19 Daniel Narvaez <dwnarvaez at gmail.com>
>
>> This code in getEnvironment is wrong, just a thinko by me.
>>
>> We should not set window.top.sugar = {} from the javascript side. Instead
>> we should if isStandalone callback({}).
>>
>
> This is related with "[web-activity] functional tests and
> env.isStandalone's current implementation" email, we were trying to do
> this, and we find with this questions...
>
>
> --
> Roger
>
> Activity Central <http://activitycentral.com/>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131220/d4cee79f/attachment.html>