Vladimir Vukicevic wrote:
> Mike Schroepfer wrote:
>> nglayout.initialpaint.delay=0
>
> This is still very much a perception thing. [...] However,
> maybe 250ms is too high of a preset these days; 100ms might be better to
> strike a balance between perception and reality. I have no idea how to
> actually test this, though.
Perhaps Beltzner, Faaborg et al have some data here, with respect to how
users perceive delays. I know there's a rough rule of thumb about having
user interfaces give feedback within ~100-500ms to avoid appearing
non-responsive; seems like there would be research in that area
applicable here.
I'm not familiar with how painting is handled, but perhaps there's also
similar data to guide how often to repaint when the page is still
loading. For example, would doing it once at 100ms and once at 500ms
(and then as needed) allow things to be both snappy and performant?
Justin
_______________________________________________
dev-performance mailing list
dev-performance@...
https://lists.mozilla.org/listinfo/dev-performance
