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 res
"asm.css" sounds fascinating.
In the case of epub, are the CSS selectors somehow unique to a subdocument as
well, or is it just the subsequent layout/rendering computation? And how
different is it from, say, an iframe?
Google and many others preprocess their layouts, so providing fast subsets
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 S
3 matches
Mail list logo
