| 39 | | |
| | 39 | * jchaffraix: maybe you shouldn't inherit from RenderBlock if you aren't actually a "block" in the CSS box model sense |
| | 40 | |
| | 41 | * eseidel: a render layer defines its own coordinate space (and a z-order) - so when you need your own coordinates (e.g., abs positioning), you need a layer |
| | 42 | |
| | 43 | ## Security Issues w/ the current architecture |
| | 44 | |
| | 45 | * jchaffraix: if the render tree gets confused, the code does bad things with pointers |
| | 46 | * jchaffraix: potentially layout should never modify the render tree (during layout) |
| | 47 | * example: don't destroy / reparent things during run-ins |
| | 48 | * inferno: e.g., during flexbox layout, this can leave other objects with dangling pointers to stale objects |
| | 49 | * rniwa: how do you handle continuations (generated content, bidirectional text)? |
| | 50 | * during style recalc? |
| | 51 | |
| | 52 | * eseidel: the render tree is really just a big cache, and maybe that's the problem |
| | 53 | * we hope that nothing is stale at that point |
| | 54 | * layout is supposed to make things not be stale |
| | 55 | |
| | 56 | * jchaffraix: are continuations strictly defined by the dom tree? |
| | 57 | * inferno: they shouldn't be (aren't) created during layout (?) |
| | 58 | * eseidel: that is not the invariant today - blocks are created and destroyed during layout |
| | 59 | * jamesr: that only happens during style recalc |
| | 60 | * eseidel: I am misinformed :) |
| | 61 | |
| | 62 | * rniwa: why do counters need to compute the counter during layout (and not style calc) |
| | 63 | * jchaffraix: dunno, need to redesign counters? possible could be done during pre layout |
