I'm wondering if you could change the bgcolor #0000099 to something else because
it's exactly the same as the text selection color. In other words it's not
possible to see what you're selecting if you're over a block with that color. A
tad annoying.
Also putting the layout stuff in a style sheet would ease updating, the
documents would become smaller and less error prone blah blah..

"clos" -> "close", will fix the size problem today.
I'm working on moving to a .css version, should be available in the next couple
of weeks. That should make the underlying code much easier to look at. The
disappearing text in table thing doesn't happen on my machine. What platform
are you using? I can certainly adjust the shade of blue if you think it would
help. The blue itself is part of the old style recommendations.

The frozen interface at
http://www.mozilla.org/projects/embedding/embedapiref/embedapi55.html#1150910
specifies nsIIOService::offline as an attribute available for setting offline mode, and the documentation does not mention SetOffline or GetOffline.
When I attempt to use the offline attribute, I get an error message stating there is no member named 'offline'.
Eventhough SetOffLine is not documented as part of the frozon interface, it does work.
Could you please clarify if 'offline' is part of the frozen interface, and please consider updating the documentation on the frozen interface to include SetOffLine and GetOffLine.
Thank You,
Don.

I have found (using XULRunner compiled from mozilla-1.9.1 sources for Firefox) that embedder-provided nsWebBrowserChrome should also implement nsIInterfaceRequestor and nsIWeakReference (other than nsIEmbeddingSiteWindow) in order used by the runtime. Could this note be added on the page ?

To follow up on this bug, archiving legacy content is now a requirement for being able to move forward with the mozilla.org/.com merge.
If there is no plan to manually migrate this content in the short term, we will go ahead with moving this content off of www.mozilla.org and putting it someplace where it can decide what to do with it on your own schedule. That may be either the www-archive.mozilla.org site or an archive section of MDN.

If no one currently owns this then archiving it makes sense. This will let people know the content is not up to date and will leave the content in a place that is available for someone to update and migrate back to an appropriate place later. I'll archive this soon unless there are objections.