Moving the atom-lists to their siblingclasses (i.e. xul-atoms should go to the xul code, svg atoms to svg code) sounds like a very good idea. I would prefer if the atomlists lived in mozilla/content/{xul|html|svg}/content, rather then in layout. I tend to think of layout as being built on top of content and that stuff that are used by both of them should live in layout. Of course, this is likly because i mostly work in content :)
Err.. this should of course say "stuff that are used by both of them should live in *layout*"
content/html/content/public/nsHTMLValue.cpp (or content/base/public/ ?)
content/html/content/src/nsHTMLValue.h (or content/base/src/ ?)
Please move both these to content/html/content/src. This class is being replaced by nsAttrValue which lives there. And neither nsHTMLValue or nsAttrValue is used (or usable) outside of content so no need to put the .h file in public.
And this should say "outside of gklayout.so" :)
It's friday, time to go home...
/ Jonas _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
