There is an issue with Firefox and ColdFusion (other languages too I would think?). When a form field name starts with the string 'priority', the Firefox browser must parse the request and use it for some Firefox function and then Firefox passes the value "u=0, i" as the value for the "priority..." form field. It's like an update was applied a few months ago and someone forgot to take out a debug function. The form field names "priority" and "priorityTest" result in Firefox passing the value "u=0, i" for the form field while form field names containing but not starting with "priority" behave as expected. For example, using "TestPriority" as the field name passes the form field value as expected and of course a field not containing priority at all passes the value as expected as well. This started a few months ago. Anyone else seeing this?
