Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Why are styles computed lazily?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Seth Fowler  
View profile  
 More options Oct 11 2012, 2:13 pm
Newsgroups: mozilla.dev.tech.layout
From: Seth Fowler <s...@mozilla.com>
Date: Thu, 11 Oct 2012 11:13:04 -0700
Local: Thurs, Oct 11 2012 2:13 pm
Subject: Re: Why are styles computed lazily?

On Oct 10, 2012, at 2:43 PM, L. David Baron <dba...@dbaron.org> wrote:

> We can never determine for sure that a given struct will
> never need a struct, since a page can always ask for a style in it
> via getComputedStyle (except for the rare style context that
> couldn't potentially be used from a getComputedStyle call).  So I
> don't see how we can keep the space optimization without also
> keeping the ability to compute lazily.

Yes, that's true. You might want the ability to do lazy style
computations, even if your primary strategy was eager, just for cases
like this. It'd be interesting to know how often it's beneficial to
not just go ahead and compute the styles for e.g. display: none
subtrees, though. Presumably they are on the page because
eventually some event will cause them to be displayed, right?
(Quite hypothetical without data, of course.)

- Seth


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.