tracker issue : CFB-3831825

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

Code Coloring Breaks When Comments Used Within Function with Named Arguments

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Dave Levin / Henweigh99 (Dave Levin)

Created: 09/25/2014

Components: Editor Features

Versions: 3.0

Failure Type: Usability Issue

Found In Build/Fixed In Build: 3.0 Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Windows 7 64-bit

Vote Count: 5

Problem Description:
Code coloring model breaks when you add a comment within a function containing named arguments.

Steps to Reproduce:
1. Open ColdFusion Builder 3
2. Create a new CFM page
3. Paste the following sample code:
<cfset myFunction(
	argument1 = "strawberries",
	argument2 = "bananas", <!--- these are my favorite --->
	argument3 = "blueberries",
	argument4 = "pineapples"
) />

Actual Result:
The code coloring feature colors everything after the comment black including the end of the tag.

Expected Result:
The code coloring should resume coloring the rest of the tag normally after the comment is closed.  Dreamweaver handles this fine. So does CFEclipse.

Any Workarounds:
Open file with CFEclipse editor instead.  Within CFBuilder there is no workaround that I know of.

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

Watson Bug ID:	3831825

External Customer Info:
External Company:  
External Customer Name: Henweigh99
External Customer Email:  
External Test Config: Windows 7 x64.

Running ColdFusion Builder 3 standalone AND as eclipse plugin.



Note: CFEclipse handles code coloring differently for functions with named arguments so please disregard the mentioning of CFEclipse in the "Expected Results" and "Workarounds" section.
Comment by External U.
26835 | September 25, 2014 11:29:43 AM GMT
All of these syntax coloring issues need to get fixed so people can stop saying "but it works in Dreamweaver".
Vote by extuser
26840 | September 26, 2014 12:09:31 AM GMT
I cannot believe I paid for this product. Honestly, if Adobe employees actually even once/week responded in their own forums, I'd be happier. The Customer Service is shoddier than the product...
Vote by extuser
26841 | October 08, 2014 07:01:31 AM GMT
There is a set of colorization bugs that we decided to fix for CFB-next. This should get added to that. (Comment added from ex-user id:dsarkar)
Comment by Adobe D.
26836 | October 27, 2014 02:49:54 AM GMT
Please fix. It is a troubling issue that I would like to see corrected.
Vote by extuser
26842 | October 27, 2014 10:49:56 PM GMT
This is a basic feature of any modern code editor/IDE.
Vote by extuser
26843 | December 03, 2014 05:40:32 AM GMT
Please fix.
Comment by External U.
26837 | December 15, 2014 01:12:21 PM GMT
How hard would it be to fix it? Please.
Vote by extuser
26844 | January 09, 2015 12:19:54 AM GMT
Issue is fixed in CFB 2016 and fix will be available via update 2 (Comment added from ex-user id:prk)
Comment by Adobe D.
26838 | May 10, 2016 05:46:23 AM GMT
So I got 3 emails on this bug and no idea what happened or changed with this. Was it corrected? Why did I get emails?
Comment by External U.
26839 | May 10, 2016 07:03:18 AM GMT