FOSI has ways of detecting empty elements, as described in the attached PDF file from my book. It occurs to me now that a FOSI could write an external ASCII file (.exp file) with information about empty elements. For example:
.exp file
chapter 2 title on preview page 12 has no content
chapter 5 title onpreviewpage 33 has no content
With this information, you could go to the Preview page and use Synchronize Editor Position to locate the empty element in the Edit window. The following code outputs "EMPTY TITLE" to make it easy to spot.
.fos fragment
<e-i-c gi="title" context="chapter">
<charlist inherit="1" charsubsetref="title" allcaps"=">
<savetext textid="chapter-title.txt" conrule="#CONTENT">
<usetext source="chapterct.txt,\." \"="></usetext>
<usetext source="<empty.yn">,</empty.yn>"></usetext>
..
<e-i-c gi="empty.yn">
<charlist inherit="1"></charlist>
<att>
<specval attname="chapter-title.txt" attloc="#FOSI" attval="#NONE">
<charsubset>
<usetext source="\EMPTY" title\"=">
<subchars charsubsetref="bold">
<highlt inherit="1" bckclr="#FF0000" fontclr="#FFFFFF">
</subchars>
</usetext>
<savetext textid="empty.app"append="1">
conrule="\chapter \,chapterct.txt,\ title onpreviewpage \,preview-pagect.txt[BO],\ has no content&#RE;\"
...
<e-i-c gi="toptag">
<charlist inherit="1">
<usetext source="empty.app" placemnt="after" userule="1">
...
