I've read the following, recently:
[...]
> In Opera, every window has its own JavaScript thread. This includes
> windows in iframes. The consequence is that event handlers initiated from
> different frames might execute at the same time. If these simultaneous
> scripts modify shared data (like pro
I know that webkitgtk is currently single web process, they are working to
make it one process per web view, but not per frame afaik. In the blink
announcement google mentioned they wanted to go one process per frame,
which was not possible to do with webkit. I don't really know if single
process i
On Thu, Dec 19, 2013 at 12:28 PM, Daniel Narvaez wrote:
> Can you explain where multi thread would be an issue in our code? Why I'm
> thinking perhaps simplistically is that we are already dealing with the
> window.sugar stuff being available asyncronously.
Yes, we dealt with this, already. But I
On 19 December 2013 17:14, Code Raguet wrote:
>
> On Thu, Dec 19, 2013 at 12:28 PM, Daniel Narvaez wrote:
>
>> Can you explain where multi thread would be an issue in our code? Why I'm
>> thinking perhaps simplistically is that we are already dealing with the
>> window.sugar stuff being available
2013/12/19 Daniel Narvaez
> 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 im
>
> 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 20 December 2013 16:54, Code Raguet wrote:
> 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???*
>
On Fri, Dec 20, 2013 at 4:38 PM, Daniel Narvaez wrote:
>
>> chrome: not mandatory
>>
>
> But likely to be mandatory in the not too distant future.
>
are you sure about this?
I thought that browsers were moving towards single-thread with webworkers
API when parallelism is needed.
I would probabl
On 20 December 2013 20:54, Code Raguet wrote:
>
> On Fri, Dec 20, 2013 at 4:38 PM, Daniel Narvaez wrote:
>
>>
>>> chrome: not mandatory
>>>
>>
>> But likely to be mandatory in the not too distant future.
>>
> are you sure about this?
> I thought that browsers were moving towards single-thread wit
On Fri, Dec 20, 2013 at 4:57 PM, Daniel Narvaez wrote:
> I know for sure that they are working on this
>
> http://www.chromium.org/developers/design-documents/oop-iframes
>
> I don't know for sure if js could be single threaded despite that.
>
thanks
_
10 matches
Mail list logo
