afri i'm not surprised that you need foreignObject and that it is in the svg namespace. Maybe foreignObject is mis-titled. I view as breaking out of a reflowing context into an absolute canvas-context, and as breaking out of a canvas context into a reflowing context afri should be called something like HHirsch then, how do you see an with an inner ? HHirsch it is interesting to learn that you think in terms of reflow context and canvas context while I just see the box of the canvas (no judgement here) afri phone brb darobin tttt darobin foreignObject doesn't necessarily break back into reflowing context darobin it breaks out of the absolute canvas, what it breaks back /into/ is another kettle of fish HHirsch I've still not got it why there is a reason to tell svg that I'm leaving when it can see that from the different namespace that comes... darobin HHirsch: it defines a box that SVG knows about and considers black darobin the xywh are the important bits HHirsch accepting foreignObject for now ;) ... are there any performance problems when I have a hierarchy being something like ? HHirsch I mean: will this result in multiple canvasses (sp?) getting created and rendered separately and only getting blended into each other at the end? HHirsch darobin: you don't mean "black" literally, such as in "background: black"?? darobin I don't know of performance problems darobin no :) the content of fO is composited HHirsch the reason is that I need to be able to combine existing XML components as users want them to be combined hierarchically. And so I might end up with a chain of several XHTML/SVG components. HHirsch darobin: fO = floating|formatting|??? objects (sorry for my limited knowledge) HHirsch And the fO's are ordered accordingly to z-index, opacity, et cetera? darobin fO = foreignObject darobin oh darobin they work just like any other SVG element, they follow the painter model darobin whatever is latest in document is above HHirsch slaps myself darobin they support opacity, transformations, etc afri darobin: The Mozilla implementation of foreignObject breaks into a reflowing context. Reflowing is the "standard" mode of operation of Mozilla. SVG is only an afterthought. Whether that's right or wrong is a good question. I was very keen on the idea of compound docs a few years ago, but I've been turned off them completely. There are just too many technical and semantic issues. =-= HHirsch is now known as HHirsch_away darobin afri: I understand, but somehow that's almost just an implementation detail darobin that is, if you put inside a fO you haven't really broken into reflowing context :) afri darobin: well, you have. the is defined in a reflowing context darobin mkay afri darobin: you can't put a into a fO darobin yes, okay, I see what you mean