On 10/2/09 12:45 PM, Boris Zbarsky wrote:
Another option is to have the analysis pass actually construct the
subtree of frame construction data for inline frames (recursing into
kids that are themselves inlines, then propagating information about
block kids up that tree) and then pass that information to
ConstructInline so that it doesn't have to recompute all that information.
Need to think about that some more.
That sounds like more work, but it does sound like the right direction.
Hmm, if you play your cards right, this might make implementing
display:run-in quite easy! Just recurse into run-ins like you recurse
into inlines; if you find a block descendant for the run-in, turn the
run-in into a block, otherwise after you've built the list you can
figure out which run-ins need to run in to which blocks or turn into blocks.
Rob
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
