On Sun, Feb 22, 2015 at 3:45 AM, Robert O'Callahan wrote:
> On Fri, Feb 20, 2015 at 9:11 PM, Jonas Sicking wrote:
>>
>> On Thu, Feb 19, 2015 at 6:27 PM, Robert O'Callahan
>> wrote:
>> > Should UIWorkers have access to the full Worker API? It seems like
>> > there's
>> > no reason not to give the
A couple thoughts from the perspective of a web app dev who has struggled with
this problem:
I get excited when I hear a proven solution with well-understood scope like
“animations and user interactions on the same thread”. I get nervous about
ambitious and unknown solutions (async DOM). The we
On Tue, Feb 24, 2015 at 8:56 AM, Jonas Sicking wrote:
> On Mon, Feb 23, 2015 at 10:56 AM, Gavin Sharp
> wrote:
> > What does it mean to "save your for later viewing"?
>
> In gmail it would mean saving the set of emails that you are currently
> looking at.
>
> For facebook it would mean the news
On Tue, Feb 24, 2015 at 7:36 AM, Jonas Sicking wrote:
> On Sun, Feb 22, 2015 at 3:45 AM, Robert O'Callahan
> wrote:
> > Your use-cases already fail today because many Web pages use scroll event
> > handlers and JS custom layouts. UIWorkers won't make the problem any
> worse.
>
> I agree that it'
On Mon, Feb 23, 2015 at 12:07 PM, Robert O'Callahan
wrote:
> On Tue, Feb 24, 2015 at 8:56 AM, Jonas Sicking wrote:
>>
>> On Mon, Feb 23, 2015 at 10:56 AM, Gavin Sharp
>> wrote:
>> > What does it mean to "save your for later viewing"?
>>
>> In gmail it would mean saving the set of emails that yo
It’s funny: I have come to the opposite conclusion for the same reason.
The Good: getting 60fps interactions and animations in web apps using a proven
approach (UI and interaction thread).
The Ideal: also automatically serializing those apps for offline use.
While I very much want the ideal to
On Tue, Feb 24, 2015 at 10:57 AM, Gordon Brander
wrote:
> It’s funny: I have come to the opposite conclusion for the same reason.
>
> The Good: getting 60fps interactions and animations in web apps using a
> proven approach (UI and interaction thread).
> The Ideal: also automatically serializing
On Mon, Feb 23, 2015 at 3:02 PM, Robert O'Callahan wrote:
> On Tue, Feb 24, 2015 at 10:57 AM, Gordon Brander
> wrote:
>>
>> It's funny: I have come to the opposite conclusion for the same reason.
>>
>> The Good: getting 60fps interactions and animations in web apps using a
>> proven approach (UI
Le 24 févr. 2015 à 08:02, Robert O'Callahan a écrit :
> Also, there is a way to get "save for later viewing" to work with complex
> apps: serialize all the application state --- DOM, CSS, JS heap, workers,
> etc --- and revive it later, possibly in a jail that blocks it from
> accessing the netwo
On Tue, Feb 24, 2015 at 12:09 PM, Jonas Sicking wrote:
> I think this would fall over more often than not.
>
> Most developers will not write their code to be resilient in the face
> of being suspended for extended periods of time. Upon reopening they
> would likely display error dialogs, or upda
On Mon, Feb 23, 2015 at 4:01 PM, Robert O'Callahan wrote:
> On Tue, Feb 24, 2015 at 12:09 PM, Jonas Sicking wrote:
>>
>> I think this would fall over more often than not.
>>
>> Most developers will not write their code to be resilient in the face
>> of being suspended for extended periods of time
> 2) UIWorker: some kind of JS worker that receives callbacks during
composition; each callback can take inputs such as time and scroll
position(s) as inputs and can update certain CSS properties (e.g.
transforms, opacity) on elements that the compositor then uses.
>
>
How should we explain the CSS
12 matches
Mail list logo
