Interesting idea: optimizing for good old-fashioned Reading :) It sounds like it's a timely discussion to have. What Layout invariants can we assume (and optimize CSS for) if hinted in advance? Can we flag these hints at the selector level?
--Jet ----- Original Message ----- From: "Benjamin Smedberg" <benja...@smedbergs.us> To: "Jet Villegas" <j...@mozilla.com> Cc: "Boris Zbarsky" <bzbar...@mit.edu>, mozilla-dev-se...@lists.mozilla.org Sent: Monday, July 1, 2013 8:41:46 AM Subject: Re: [dev-servo] Selector matching in Rust On 6/30/13 2:53 AM, Jet Villegas wrote: > I'd love to see us make some bold moves here for application development use > cases (think asm.js for CSS.) Can we define a strict subset of CSS syntax > with clear semantics for parallel processing, raster caches, hardware > acceleration, and general app responsiveness? Well, not sure about for *apps*, but there is certainly opportunity for improvement if you limit CSS. Specifically, there's the subset of CSS used in epub, which disallows absolute or fixed positioning and I think other things like negative margins. This allows you to guarantee that layout always flows forward and you can easily paginate the document and at least in theory allows for a bunch of layout optimizations. It also specifically allows you to lay out documents starting "anywhere" (as an ebook reader does) without building the entire DOM. It would be nice if the web could have efficient paginated documents without all the horrible positioning added to support "apps". --BDS _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
