| | 25 | |
| | 26 | * eseidel: what are the problems we're trying to solve? |
| | 27 | * (??) need render layers to support z-index (for svg 2.0 and z-stacking not in document order) |
| | 28 | * jamesr: we want to composited into svg |
| | 29 | * enne: rendering / layers are hard to test |
| | 30 | * dave barton: mathml is very painful - math layout is bottom-up from the children of the node, not top-down left-to-right on the page |
| | 31 | * jamesr / jchaffraix: tables are very similar |
| | 32 | * eseidel: if you call setNeedsLayout(False), you should be able to do whatever you want inside your own elements |
| | 33 | * jchaffraix: this means we don't reuse other code |
| | 34 | * eseidel: there are other layout models other than the renderboxmodel |
| | 35 | * eseidel: also there's computePreferredWidths() |
| | 36 | * dave barton: this is kinda what he does in mathml |
| | 37 | * jamesr: maybe mathml shouldn't be deriving from renderboxmodelobject? |
| | 38 | * dave barton: but we do use a lot of it - maybe this is more a question about writing your own render object and should be in the other talk? |
| | 39 | |
| | 40 | |
| | 41 | |
| | 42 | |
| | 43 | |
