ColdFusion 2016 Upgrade: CFLayoutarea content not displaying in UI

We experienced the same issue here. The fix for us was to add width and height to the tag:

<cflayoutarea style="width:1050;height:650;"title="Test1">

Same problem here.  I can't seem to get it to work with any source="" attribute.

<cflayout name="mainLayout" type="tab" >

      <cflayoutarea name="tab_mainTab" title="My Title" source="/temp.cfm" />

</cflayout>

Where temp.cfm contains simply "hello world".  The tab spins for a second and then goes blank.  If I point it to temp2.cfm (which doesn't exist), I get an error.  If I put a database call in temp.cfm, it gets executed, so I know it's being called correctly.  But, nothing showing up in the tab.

Two suggestions which may or may not solve your problem, but will improve the code:

1) If the page valuations.cfm itself contains a Coldfusion UI tag, then you should have cfajaximport tag at the beginning of the page.

2) The statements

<cfset runID = valuationRuns.RunId[currentrow]>

<cfset runName = valuationRuns.RunName[currentrow]>

confuse the names of new variables with those of database column. Modify your code to something like

<cfloop query="valuationRuns">

   <cfset rnID = valuationRuns.RunId[currentrow]>

   <cfset rnName = valuationRuns.RunName[currentrow]>

   <cflayoutarea title="Run #valuationRuns.RunId[currentrow]##IIF(Left(valuationRuns.RunName[currentrow],5) NEQ 'RunID',DE(' - #valuationRuns.RunName[currentrow]#'),DE(''))#" source="./valuations.cfm?test_record_id=#testId#&test_name=#URLEncodedFormat(test_name)#&runId=#rnId#&runName=#URLEncodedFormat(rnName)##IIF(StructKeyExists(URL,'ID'),DE('#variables.ID#'),DE(''))#"

   refreshonactivate="true" overflow="hidden" style="height:570px;" ></cflayoutarea>

   </cfloop>

Have you been able to resolve this?

I have never used <CFLAYOUT> or <CFLAYOUTAREA>, but I do know that the underlying JavaScript library that CF uses to power those features (I think it's ExtJS) has been updated to a newer version in CF2016.  It could be that arguments on those tags have changed or the expected values/datatypes of those arguments changed.  Have you looked at the 2016 docs for those tags? I just checked and see no changes since CF9.

Do you have any custom JavaScript on your page that modified the behavior of the tab interface?