2013/5/6 Robert O'Callahan <rob...@ocallahan.org> > We expose HTML and SVG content to Web applications by structuring that > content as a tree and then exposing it using standard DOM APIs. These APIs > let you examine, manipulate, parse and serialize content subtrees. They > also let you handle events on that content. CSS also depends on content > having a DOM tree structure for selectors and inheritance to work. You > definitely need to able to handle events and apply CSS to elements of your > math markup. >
I guess I don't see the usefulness of allowing to apply style to individual parts of an equation --- applying a single style to an entire equation would be plenty enough as far as I can see. Regarding editing, if I understand correctly, you have WYSIWYG or other kinds of fancy editing in mind, where understanding of the syntax tree inside of the equation is needed; I haven't seen a need for WYSIWYG editing of math, but I don't want to try to fight the war "for or against WYSIWYG". Benoit > > I mentioned editing because I thought you'd want to reuse DOM text node > editing in a MathML editor. > > Introducing a new kind of document markup that can't be manipulated via > DOM APIs is a non-starter. And of course, once you've figured out how to > expose math content in a DOM API, people are going to expect the source > language to use HTML-like angle-bracket syntax like everything else that > parses to a DOM. > > Rob > -- > q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q > qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq > qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq > qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq > qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q > qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q" > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
