#7353 closed defect (fixed)
ValidationTextBox: problem with and ASP.NET AJAX
Reported by: | detroitpro | Owned by: | Douglas Hays |
---|---|---|---|
Priority: | high | Milestone: | 1.4 |
Component: | Dijit - Form | Version: | 1.0 |
Keywords: | ValidationTextBox, ASP.NET AJAX, ESRI | Cc: | |
Blocked By: | Blocking: |
Description
Error when using ValidationTextBox? and ASP.NET AJAX on same page.
It seems that both call create a function called Number.function and error out when used together.
Error:
[Exception... "'Sys.ParameterCountException?: Sys.ParameterCountException?: Parameter count mismatch.' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0×8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "<unknown>" data: no]
Note: The I am using the hosted version of the toolkit from ESRI, it makes up basis for their JavaScript? API.
www.esri.com
Change History (7)
comment:1 Changed 14 years ago by
Component: | General → Dijit |
---|---|
Owner: | changed from anonymous to Douglas Hays |
Summary: | dijit.form.ValidationTextBox and ASP.NET AJAX → ValidationTextBox: problem with and ASP.NET AJAX |
comment:3 Changed 13 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
No testcase was ever provided.
comment:4 Changed 12 years ago by
Note for completeness that this was fixed in Dojo 1.4, but is an issue with 1.3. Here are a pair of testcases:
http://jsfiddle.net/RAUA7/1/ (1.4) http://jsfiddle.net/RAUA7/2/ (1.3)
comment:5 Changed 12 years ago by
Milestone: | future → 1.4 |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
comment:6 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:7 Changed 11 years ago by
Component: | Dijit → Dijit - Form |
---|
Certainly we would need a test case to reproduce this and I doubt anyone will be willing to install ASP.NET to run a test, but given that dojo is client side only, you should be able to come up with a plain HTML file (based on whatever is generated from ASP.NET) the reproduces the problem.
Try to come up with as small a test case as possible.