tracker issue : CF-4198781

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

4195407 BUG NOT FIXED

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Alberto Genty / Alberto Genty ()

Created: 05/26/2017

Components: CFForm

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: 11,0,12,302575 /

Priority/Frequency: Normal / All users will encounter

Locale/System: ALL / Win 2008 Server R2 64 bit

Vote Count: 0

Problem Description:
This update breaks Chrome on windows and macs... 
Browsers that support the HTML 5 input type="date" will override CFUI controls.

Steps to Reproduce:
(1) Create & run a .cfm file containing the following code in Google Chrome for Mac or Windoes
	<cfform action="action.cfm" method="post" name="test">
		<cfinput type="datefield" name="date">
	</cfform>
	(2) View source and locate input tag

Actual Result:
<input name="date" id="date"  type="date" class="datefieldinput"  />
Expected Result:
<input name="date" id="date"  type="text" class="datefieldinput"  />

Any Workarounds:
None

Attachments:

  1. May 26, 2017 00:00:00: Screen Shot 2017-05-25 at 8.31.56 PM.png

Comments:

Most of our customers use Chrome. Because of this issue, the security fix associated with this release cannot be deployed to our production environment either... As such, this leaving us vulnerable.
Comment by Alberto G.
673 | May 26, 2017 02:00:07 AM GMT
Marking as duplicate of bug #CF-4198570. Hi Alberto, You can refer the bug CF-4198570 and can apply the patch provided in the same bug. Thanks, Mukesh
Comment by Mukesh K.
674 | May 26, 2017 06:12:07 AM GMT
Thanks Mukesh. To be clear, this is not a duplicate bug. 4195407 addressed the issue regarding the 'datefield' input type (which is not valid). In an attempt to fix that bug, a new bug was introduced by rendering the input type as 'date' which breaks HTML 5 compliant browsers. As such, the issue affected Google Chrome (mac and windows). As a result, this is a new bug that can be resolved by rendering a input type of text. Please be sure to test Google Chrome.
Comment by Alberto G.
675 | May 26, 2017 08:12:25 AM GMT
Hi Adobe, This ticket's status/reason is: Closed/Duplicate. But customer says it is not a duplicate. Please review customer's last comment. Thanks!, -Aaron
Comment by Aaron N.
676 | July 09, 2017 11:05:31 PM GMT
Hi Aaron, The fix for bug #CF-4195407 will be available in the upcoming update. I have mentioned the bug#CF-4198570 for the reference of patch and we had opened the bug#CF-4195407 . Thanks, Mukesh
Comment by Mukesh K.
677 | July 10, 2017 05:20:31 AM GMT