Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

Tooltip exception: Unable to get property 'prop' of undefined or null reference. #2785

Closed
VitalyVoroshilov opened this issue Oct 6, 2014 · 11 comments

Comments

VitalyVoroshilov added a commit to VitalyVoroshilov/bootstrap that referenced this issue Oct 6, 2014
@chrisirhc
Copy link
Contributor

I'm not sure what you mean. Can you create a Plunker and describe the steps to reproduce this issue?

@VitalyVoroshilov
Copy link
Contributor Author

http://plnkr.co/edit/KpsACpxZ2LbdbEzHEFPl?p=preview
Try to move from 1 to 2, so that 1has not yet appeared... It's not easy to reproduce...

@herringtown
Copy link

@VitalyVoroshilov , @chrisirhc any update on this? I experience this one frequently -- steps to replicate are extremely, extremely hard to pin down.

@brandonkboswell
Copy link

+1

@cgallarno
Copy link

+1 for this too

@wesleycho wesleycho added this to the Backlog milestone Mar 23, 2015
@tomauty
Copy link

tomauty commented May 15, 2015

Pretty sure this is IE10 only

@charwking
Copy link

I've been able to reproduce this in Chrome and Firefox. After some digging, I'm fairly sure this change, available in v0.13.0 has resolved the issue.

@wesleycho
Copy link
Contributor

I cannot reproduce this, as shown in this Plunker based off of current master.

Closing as resolved - if this is still an issue, feel free to comment here or create a new ticket.

@tsclaus
Copy link

tsclaus commented Nov 2, 2015

I am still getting a similar error with a fairly new version (0.13.4)

Stacktrace:

Uncaught TypeError: Cannot set property 'isOpen' of null
    hide @ ui-bootstrap-tpls.js:3496
    TooltipBind @ ui-bootstrap-tpls.js:3454

Given the local variable name for null is ttScope and the tooltip directive creates its own scope with that property, I am fairly certain this error is caused by an asynchronous piece of tooltip code trying to access a scope that angular has already destroyed (which is somewhat hard to reproduce).

I will update to .14.3 and see if the error still happens (thought it only happens randomly once or twice a day during development).

@icfantv
Copy link
Contributor

icfantv commented Nov 2, 2015

@tsclaus, please also try against a build from master so we can try to narrow this down to either a user issue or possibly a release-specific issue. If it still happens in your code, please open a new issue following these instructions. New comments on closed (and really old) issues is a good way for them to get lost. Thanks.

@josephhelmrich
Copy link

This still occurrs in v2.1.3. The problem is that the if (!tooltip) check is outside of the $timeout() code. It needs to be moved into the $timeout code to ensure this error doesn't occur

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests