On Sat, Feb 14, 2015 at 9:21 AM, Ted Mielczarek t...@mielczarek.org wrote:
On Fri, Feb 13, 2015, at 11:43 AM, Nathan Froyd wrote:
On Fri, Feb 13, 2015 at 1:40 AM, Gregory Szorc g...@mozilla.com wrote:
Truth be told, unless you are collaborating with other people using
evolution, the
Reluctantly replying to this, as a complete non-authority on the subject.
I like the idea of “in pages that drop below…” part, where we decide between
sync and async scrolling based on performance criteria. I don’t know what it
would take to implement, but it seems like a reasonable heuristic
On Sunday, February 15, 2015 at 4:48:06 PM UTC-5, Robert O'Callahan wrote:
Their current idea is to add a new CSS property scroll-blocks-on to let a
page opt into sync scrolling:
https://docs.google.com/document/d/1aOQRw76C0enLBd0mCG_-IM6bso7DxXwvqTiRWgNdTn8/edit#
In pages that drop below some
On Sun, Feb 8, 2015 at 3:37 PM, Xidorn Quan quanxunz...@gmail.com wrote:
Before the next merge day, I intent to turn on CSS Ruby by default on all
platforms if all rest blockers can be fixed by then. It has been developed
behind |layout.css.ruby.enabled| for a while.
This would add 5 new
4 matches
Mail list logo
