tracker issue : CF-3037144

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 74756:(Watson Migration Closure)Conditions:Empty input in CFINPUT, causes the CFLAYAOUTAREA to duplicate itself.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Tariq Ahmed / Tariq Ahmed ()

Created: 12/24/2008

Components: AJAX, UI Components

Versions: 9.0

Failure Type:

Found In Build/Fixed In Build: 0000 / CF11 Update5

Priority/Frequency: Normal / Few users will encounter

Locale/System: English / Platforms All

Vote Count: 1

Listed in the version 11.0.05.293506 Issues Fixed doc
Problem:

Conditions:
- One AutoSuggest CFINPUT
- Inside of a  CFLAYOUTAREA
- No other Form Inputs

Bug:
- If you just hit enter into that empty CFINPUT, it causes the CFLAYAOUTAREA to duplicate itself. But if you type something in and hit enter, it works fine, or if there is at least one other form input it works.
Method:

<cflayout name="search" type="tab">
  <cflayoutarea name="abc" title="ABC" style="height:200">
    <cfform name="myform" method="POST">
      <cfinput type="Text" name="Something" autosuggest="cfc:CF9Tests.LayoutIssue2.test.findSomething({cfautosuggestvalue})">
    </cfform>        
  </cflayoutarea>     
</cflayout>

The CFC doesn't even need to exist, just load up the code, click into the input and hit enter.

This is an existing bug in CF8 as well.

Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3037144

External Customer Info:
External Company:  
External Customer Name: Tariq Ahmed
External Customer Email: 755462B744617992992015D5
External Test Config: 12/24/2008

Attachments:

Comments:

[vmannebo 4/14/09] Need to trap the "enter" event to prevent a form submission. Bug History Timestamp|name|field|from value|to value| 24 Dec 2008 11:49:21 GMT | Tariq Ahmed | Bug Submitted | | | 24 Dec 2008 11:49:21 GMT | System System | Class Type | | BUG | 24 Dec 2008 11:49:21 GMT | System System | Severity | | 4-Important (Easy workaround, should be fixed) | 19 Jan 2009 20:02:21 GMT | Praveen Gupta | Priority | | B | 19 Jan 2009 20:02:21 GMT | Praveen Gupta | Queue Transfer | | bhakti | 19 Jan 2009 20:02:21 GMT | Praveen Gupta | Target Fix Milestone | | Beta 2 | 19 Jan 2009 20:02:21 GMT | Praveen Gupta | Target Fix Release | | ColdFusion 9.0 | 30 Mar 2009 23:42:30 GMT | Bhakti Pingale | Queue Transfer | bhakti | awdhesh | 30 Mar 2009 23:42:30 GMT | Bhakti Pingale | Verified | No | Yes | 13 Apr 2009 23:26:47 GMT | Vamseekrishna Manneboina | Target Fix Milestone | Beta 2 | RC 1 | 11 May 2009 02:20:39 GMT | Vamseekrishna Manneboina | Target Fix Milestone | RC 1 | Under Review | 23 Mar 2010 17:13:05 GMT | Awdhesh Kumar | Queue Transfer | awdhesh | Bugs - Neo |
Comment by Kunal S.
24315 | November 10, 2011 03:49:35 PM GMT
Actually a quick update. It doesn't have to be an auto-suggest cfinput, just any single cfinput. <cflayout name="search" type="tab"> <cflayoutarea name="abc" title="ABC" style="height:200"> <cfform name="myform"> <cfinput type="Text" name="Something"> </cfform> </cflayoutarea> </cflayout>
Vote by External U.
24322 | November 10, 2011 07:10:28 PM GMT
fix to be made available in a future CF11 udpate.
Comment by Piyush K.
24316 | January 19, 2015 09:24:17 AM GMT
The fix for this bug is available in the pre-release build of ColdFusion 11 Update 5
Comment by CFwatson U.
24317 | February 20, 2015 09:22:23 AM GMT
Adobe, This is not completely fixed in CF11 Update 5 (and build 11.0.0.294632). It is only fixed if the form has a single input: <cflayout name="myLayout" type="tab"> <cflayoutarea name="myLayoutArea" title="title"> <cfform> <cfinput type="text" name="myText"> </cfform> </cflayoutarea> </cflayout> It is broken if the form has multiple inputs: <cflayout name="myLayout" type="tab"> <cflayoutarea name="myLayoutArea" title="title"> <cfform> <cfinput type="text" name="myText"> <cfinput type="radio" name="myRadio" value="my radio"> </cfform> </cflayoutarea> </cflayout> <cflayout name="myLayout" type="tab"> <cflayoutarea name="myLayoutArea" title="title"> <cfform> <cfinput type="text" name="myText"> <cfinput type="checkbox" name="myCheckbox" value="my checkbox"> </cfform> </cflayoutarea> </cflayout> <cflayout name="myLayout" type="tab"> <cflayoutarea name="myLayoutArea" title="title"> <cfform> <cfinput type="text" name="myText"> <cfinput type="button" name="myButton"> </cfform> </cflayoutarea> </cflayout> <cflayout name="myLayout" type="tab"> <cflayoutarea name="myLayoutArea" title="title"> <cfform> <cfinput type="text" name="myText"> <cfselect name="mySelect"></cfselect> </cfform> </cflayoutarea> </cflayout> Just click on any form field, then press the Enter key, and see the tab was duplicated. Same issue exists if the layout's type is changed to "border" (and probably any other type). Can this ticket please be re-opened and fixed completely? Thanks!, -Aaron
Comment by External U.
24318 | August 13, 2015 11:17:19 PM GMT
Aaron/Tariq, If the cfform tag does not have the action attribute set, it defaults to the current script. for example the following test.cfm page : <cfform name="layoutform" method="POST"> <cfinput type="Text" name="inputbox"> </cfform> will generate the following html code: <form name="layoutform" id="layoutform" action="/layout/bugs/test.cfm" method="POST" onsubmit="return _CF_checklayoutform(this)"> <input name="inputbox" id="inputbox" type="text"> </form> This is what is causing the duplication. So, the issue in this bug will only manifest if the cfform does not specify the action attribute, Fixing this would be at the cost of changing this default behavior in case the cfform tag is used inside layout control. But that can interfere with cases where this is behavior is desired. Example: <cfif isdefined("inputbox")> Form submitted!! logic to process form. <cfabort> </cfif> <cflayout name="layoutcontainer" type="tab"> <cflayoutarea name="layoutarea" title="Text Input"> <cfform name="layoutform" method="POST"> <cfinput type="Text" name="inputbox"> </cfform> </cflayoutarea> </cflayout> If you remove the if block, in the code above you can observe the issue. But the issue can be easily handled by using the action attribute. Thoughts?
Comment by Piyush K.
24319 | April 28, 2016 10:35:03 AM GMT
Verified this is completely fixed in CF2016 Update 1 (build 2016.0.01.298513). The issue I mentioned on 08/13/2015 23:17:19 GMT (issue not fixed if form contains 2+ fields) still exists in CF11 Update 7 (build 11.0.07.296330), but is fixed in 2016.0.01.298513. Sorry, Piyush, for the late reply. This issue should be listed in CF2016's list of Issues Fixed. Thanks!, -Aaron
Comment by Aaron N.
24320 | August 08, 2017 02:16:34 AM GMT
Specifically, CF-3037144 should be listed in https://helpx.adobe.com/content/dam/help/attachments/cf2016-issues-fixed.pdf. Thanks!, -Aaron
Comment by Aaron N.
24321 | August 08, 2017 02:20:07 AM GMT