> I had previously thought that the above-mentioned problem (now fixed)
 > was responsible for the frame increasing in size with the example
 > labeled BROKEN.  I see now that the difference between the WORKING
 > example and the BROKEN example is caused by the fact that
 > `frame-after-make-frame` has already run in the WORKING example before
 > `set-face-attribute` is called with the `font` parameter.  If we
 > modify `x-create-frame-with-faces` by commenting out
 > `(face-set-after-frame-default frame parameters)` and move that over
 > to `make-frame` following `(frame-after-make-frame frame t)`, then
 > both examples work as expected.
 >
 > I understand that may not be the preferred solution, but at least we
 > know for sure that calling `frame-after-make-frame` BEFORE
 > `set-face-attribute` fixes the problem with the frame expanding even
 > though `frame-inhibit-implied-resize` is set to `t`.

Yes.  I forgot that we try to keep the number of lines and faces
constant when making the initial frame.  Try the attached patch.  It
should cover everything we have investigated so far.  Unfortunately, it
won't work with an internal tool bar like we have on Lucid, Motif, and
Windows.  There's something I haven't fathomed yet :-(

martin