J
Joe Fallon
When you move the mouse over a bar in this chart, the arrow cursor is
supposed to change into a hand cursor under certain conditions.
Those conditions are evaluated using client side javascript.
The key point here is that the javascript code ran correctly in VS 2005 and
..Net 2.0.
After upgrading to VS 2008 and .Net 3.5 the javascript runs differently!
For example, the variables for column_label and row_label are supposed to be
strings like this:
"Dec 31, 2007" and "N/A"
When the javascript function runs the chart sends these values to the
function as parameters.
In VS 2008 the parameters to the function are url encoded!
So instead of the values above you get these:
"Dec 31%2c 2007" and "N%2fA"
So the rest of the code which is expecting the correct values is now broken.
I fixed the specific functions for the chart by changing it to:
decodeURIComponent(column_label)
decodeURIComponent(row_label)
But I am very worried about the possible effects this change may have on our
javascript code everywhere else in the application.
Why is this happening happening? What has changed?
Some pages in the application use AJAX. Could that be affecting things?
Also, is there a Setting that can be used to get the old behavior?
Joe
supposed to change into a hand cursor under certain conditions.
Those conditions are evaluated using client side javascript.
The key point here is that the javascript code ran correctly in VS 2005 and
..Net 2.0.
After upgrading to VS 2008 and .Net 3.5 the javascript runs differently!
For example, the variables for column_label and row_label are supposed to be
strings like this:
"Dec 31, 2007" and "N/A"
When the javascript function runs the chart sends these values to the
function as parameters.
In VS 2008 the parameters to the function are url encoded!
So instead of the values above you get these:
"Dec 31%2c 2007" and "N%2fA"
So the rest of the code which is expecting the correct values is now broken.
I fixed the specific functions for the chart by changing it to:
decodeURIComponent(column_label)
decodeURIComponent(row_label)
But I am very worried about the possible effects this change may have on our
javascript code everywhere else in the application.
Why is this happening happening? What has changed?
Some pages in the application use AJAX. Could that be affecting things?
Also, is there a Setting that can be used to get the old behavior?
Joe