search envelope-o feed check
Home Unanswered Active Tags New Question
user comment-o

jscript runtime error: 'this.nav.top.style' is null or not an object error

Asked by mrplatypus
10 years ago.

I am seeing a lot of: jscript runtime error: 'this.nav.top.style' is null or not an object error.

Is this a known problem?
Is there a solution?

Thanks

mrplatypus (Dave)

Answer posted by Dan Letecky [DayPilot]
10 years ago.

This means the client-side object has lost the reference to the DOM placeholder.

This happens if you try to use a control that has been disposed by calling .dispose() on the client side.

Let me know if this is not the case.

Comment posted by mrplatypus
10 years ago.

Dan,

As far as I am aware, there aren't any explicit ".dispose()" calls on the daypilot controls which are in use.

Dave

Comment posted by Dan Letecky [DayPilot]
10 years ago.

Dave-
1. What is the version of the DLL that you are using?
2. Is the control inside an UpdatePanel?

Comment posted by mrplatypus
10 years ago.

Dan,

I am using DayPilot.dll v8.1.3469.1..
Yes, I am using UpdatePanels throughout the application to provide a more fluid UX.

Dave

Comment posted by mrplatypus
10 years ago.

Dan,

Also: we are currently using IE8, .Net Framework 4.0 .. Plans are in place to go to IE11... Could that be a contributing factor?

Dave.

Comment posted by mrplatypus
10 years ago.

.. I also note that in Firefox Nightly, the errors are fewer.

Comment posted by Dan Letecky [DayPilot]
10 years ago.

When exactly does it happen? Is it during any specific action?

Comment posted by mrplatypus
10 years ago.

Dan,

Apologies, I can't be specific as I can't narrow things down..

I think that it is either with the Daypilot Menu control or the DayPilot Calendar control
I am using an Ajax Update Panel.. Could that be a part of the problem?

Thanks

Dave

Comment posted by Dan Letecky [DayPilot]
10 years ago.

I mean, does it happen on the initial page load or after some user action (clicking something....)?

The best thing would be if you were able to reproduce it using a simple standalone page... So I can reproduce the issue.

Comment posted by G
9 years ago.

I'm also getting this on resizing the screen or scrolling.

This question is more than 1 months old and has been closed. Please create a new question if you have anything to add.