X is not good at doing this kind of thing. Also, removing loud and numerous debugging messages has revealed the fact that the xlib version is actually faster than the gtk version now even though it doesn't compress expose events or use shared pixmaps or shared images yet. It's going to spank when performance becomes a priority. Today what we do is we repaint the entire visible area when processing a reflow command. The plan going forward is to have each frame damage the dirty area within its frame rect.
Bug fixes to text and html output.
Work on defining block vs. inline tags in a way which will be usable from different parts of the product. Some porting issues remain with other aspects of Mozilla, but it looks like JavaScript is in the clear. Thanks - every bit helps. This brings the ECMA standard up to date with de facto JavaScript and adds some important features such as the ability to catch errors and better support for regular expressions. We're having an ECMA meeting next week.