I am also getting the error on first reload, but i do not have any response. I have a update panel which contains a update progress and a second update panel. My update progress will be visible when the second update panel refreshes. I was also having this problem. It was so sporadic that I never really bothered to try and fix it. But now it seems to be happening with some frequency.
This thread really helped. Thank you! Then in the containing page there is another UpdatePanel wrapping the UserControl. I'll let you know if it creeps back up on me. Hey whatispunk - that works a treat - as it only seemed to happen if someone clicked a button before the page fully loaded, whilst annoying, it wasn't high priority - but I'm glad to be able to add that to the list of possible niggle cures.
Not sure if there has been a fix for this one, but I ran into this problem today and it appears that a minor update say executed from a stored procedure executes too quickly for the UpdateProgress control to indicate an update or the like is in progress. I however still want to indicate to the user that an update is in progress so I added a System. Sleep to my code to explicitly delay the process. The Update progess then appears as you would expect no javascript error.
Not the most effecient way by causing a deliberate delay but it works and you dont have to move the UpdateProgress control outside of the UpdatePanel. Why on Earth would you want to force your application to be slower for the sake of a progress animation? The default is ms. And if you really must provide a sleep time, don't make it 3 seconds. Make it ms. I'm sorry if you think this is rude, but adding that sleep call is just ghastly programming, and I feel bad for your users.
There are better solutions. I for the life of me can not log in to my user account so have resorted to creating a new one Well, the "javascript hack" is a much better solution than a 3 second timeout. So if you are looking for a better suggestion then there it is. Try looking at the source of your page when you have an UpdateProgress on it. You will find the "javascript hack" sitting right in there. Because that is the actual way the update panel works. But the mere fact that you have to code this javascript on your own instead of having the framework generate it for you may seem like a hack or a work around, but it is in fact a much more solid solution.
The UpdateProgress control is also not a very good control if you ask me. It suffers from many limitations. I'm glad that you agree that "deliberately delaying a thread is definitely not the ideal approach", and I still stand by my word that it is a "ghastly" fix.
And the fact that someone would rather do that than use some javascript to fix the problem implies to me that they hadn't looked hard enough for a "better suggestion". And yes, keeping your users informed about the application's state IS very important. That's all a user needs to know that their button click just happened. And by using the javascript I can guarantee exactly when my users will see that progress occurring.
How about putting a status bar at the bottom of your page. Don't get all defensive because I'm trying to teach you something. It sounded to me like you were alright with your fix, and that to me was unfortunate and unacceptable and deserved a strong response in order for you to see the "ghastly" error of your ways.
I am getting this error too and have tried putting the update progress outside of the update panel in fact VS complains if you don't do this. The UpdateProgress control won't show or will misbehave in numerous situations. Imagine that your UpdatePanel is triggered by a control located outside of it and that UpdatePanel has an UpdateProgress either in it, or outside it using the TargetUpdatePanel property it will not display the progress.
Now, this may have been fixed since the last time I used the UpdateProgress, but I refuse to use it again, when the javascript method is so much stronger. The JavaScript is basically what the UpdateProgress injects into the page anyways, so why not write it yourself and gain full control of it. This is in milliseconds. No annoyance alert at all since 2 months ago. All IEs version are keep giving a crap feeling on my codes. It should be patched of course. Hello Mr Gates. Don't know if this will help anyone else, but I had this problem recently and seem to have solved it for now, anyway!
JavaScript was running on the client click, so I added a reference to the javascript file to the script manager. I also moved the update progress controls outside of the update panels they were in even though they were not the update panels they were linked to. I also added the delay of 50 ms to each one. I was getting this problem quite regularly too when clicking tab panels very quickly before the page posts back.
I moved the UpdateProgress outside of the UpdatePanel and all was well. However, now it is happening again despite the fix I just stated. When I click a button which controls a AJAX collapsible panel to expand and contract, if I click the button again before the page has post back I get the dreaded error below:.
A runtime error has occurred. Do you wish to debug? Error: 'this. How do I get round this problem? Come on Microsoft its hard enough debugging my own code without having to do yours too!
As a side note, this problem doesn't occur in Firefox 3 but occurs in IE 7. In fact, I've removed my update progress controls altogether and I still get the error.
Basically in a user control, I've got two update panels. On the second one, I've added a tabcontainer. On the initial load, it's fine. But any time I do anything on the page, I get the "this.
I've tried to cut it down a lot. Kevin Top achievements Rank 2. Kevin asked on 25 Mar , PM. Trying to get things working regarding skins and moving from Q3 to Q1 version. I have read the other posts and have submitted a ticket to get some help converting a custom skin. But while waiting on that, we are getting the following error on pages. Anyone else seen? When page loads, javascript error is: 'styleSheet' is null or not an object Can't tell for sure where it's coming from.
Anyone else seeing this? Add a comment. Submit comment. Sort by Score Date. Todd Anglin Top achievements Rank 2. I think the problem is what you're talking about here, but I can't understand what to do with my code Keep in mind here we should be a guest unless user is in IE! Or the JS file? AddMarker marker, label ;'; else echo ' map. A bug in the code tag software means that the code will have to be split up across multiple posts.
Welcome to TSDN! A lot of code to decipher! So, is that the error that you're getting null or not an object? Which line does it occur on? The error occours on line of the first chunk of code But I'm realizing it could be related to the header of the XML file created by function on line 1 of the second chunk FF goes straight like a train! Can you help me with this? Check if responseXML is correct by alerting it.
Is it as you expect it to be? I can't understand what I have to do Can you post the code? I'm not a PHP programmer, I just took that code and trying to make it work Between lines and , add an alert: alert xmlDoc. Is it the expected XML? This is what it does with FireFox:??? What could be then? Timings problems? How could then I solve? Tnx, PS. But the best thing is that now, when I click OK in the alert box with IE, the code works as it is expected to do!
That's strange. The ready state is already 4, so the alert shouldn't make a difference. If you check the documentElement, is that also an object? I don't know if that makes a difference. Yes it is. I did already change it But now it comes the unbelievable thing: I've just removed the alert XmlDoc ; and all is working fine even with IE
0コメント