dzhavat wrote:Interesting because I'm using an IE11 emulator and everything's working fine ...
Tooltip: critical error (!)
-
- Posts: 40
- Joined: 22 Nov 2016, 11:51
Personally, I'd recommend a very small change that protects against this kind of problem.
In the tooltip.ts source, change
to
This doesn't solve the problem at the root, but it replaces an error message with the minor annoyance of a tooltip that is prematurely removed.
In the tooltip.ts source, change
Code: Select all
hide() {
this.container.style.display = 'none';
document.body.removeChild(this.container);
this.container = null;
}
Code: Select all
hide() {
if (!this.container) {
return;
}
this.container.style.display = 'none';
document.body.removeChild(this.container);
this.container = null;
}
-
- Posts: 40
- Joined: 22 Nov 2016, 11:51
Thank you very much!
Will this issue fixed in the next release?
Will this issue fixed in the next release?
I hope you're not asking me. I'm a user, just like you...
It seems you're the only one seeing this bug. If I were you, I'd take the ts source for the tooltip component (https://github.com/primefaces/primeng/b ... tooltip.ts), put it in my project, and insert a console.log(e) before line 33. I may be wrong, but it seems that the mouseleave event is called twice in your application. See if my fix works (previous post). Inspect the events to figure out where the extra event comes from, if that's what's happening.
It's not always easy to catch the attention of the powers that be here. But if you provide enough details, you can present a more convincing case. (I'd test on IE11 if it was not so difficult to make it work with virtual hosts on my wamp server).
It seems you're the only one seeing this bug. If I were you, I'd take the ts source for the tooltip component (https://github.com/primefaces/primeng/b ... tooltip.ts), put it in my project, and insert a console.log(e) before line 33. I may be wrong, but it seems that the mouseleave event is called twice in your application. See if my fix works (previous post). Inspect the events to figure out where the extra event comes from, if that's what's happening.
It's not always easy to catch the attention of the powers that be here. But if you provide enough details, you can present a more convincing case. (I'd test on IE11 if it was not so difficult to make it work with virtual hosts on my wamp server).
-
- Posts: 40
- Joined: 22 Nov 2016, 11:51
I asked support team.
But thank you very much!
I can fix it in the sources but it isn't solution. We have to fix by update only.
But thank you very much!
I can fix it in the sources but it isn't solution. We have to fix by update only.
-
- Posts: 40
- Joined: 22 Nov 2016, 11:51
mmikeyy, could you reproduce this issue in IE11?
Did you try?
Did you try?
I just made a series of tests to try to get this error with IE11 and other versions. No luck.
You should insert the console.log statements that I suggested and see what event causes the calls to the hide method. If I remember well, a mouseleave used to be emitted when one navigated within the button, from the button element itself to a span within. Of course, the span being a child of the button element, this was a false signal. I don't know how they fixed that exactly, but they did.
I've been the only one complaining about several bugs in the past. The only way I could get anyone's attention was by explaining exactly how it could be reproduced.
To answer your last question, no error when running the plunker in IE11.
You should insert the console.log statements that I suggested and see what event causes the calls to the hide method. If I remember well, a mouseleave used to be emitted when one navigated within the button, from the button element itself to a span within. Of course, the span being a child of the button element, this was a false signal. I don't know how they fixed that exactly, but they did.
I've been the only one complaining about several bugs in the past. The only way I could get anyone's attention was by explaining exactly how it could be reproduced.
To answer your last question, no error when running the plunker in IE11.
-
- Posts: 17
- Joined: 09 Dec 2016, 17:53
Hi,
I can reproduce this error in Plunker too.
When the console is open the emulator "Edge (Standard)" is selected.
It's a normal IE 11 I use, not a Edge Browser with IE 11 emulation.
I can reproduce this error in Plunker too.
Code: Select all
EXCEPTION: Error in app/app.template.html:2:0 caused by: Die Eigenschaft "style" eines undefinierten oder Nullverweises kann nicht abgerufen werden.
ORIGINAL EXCEPTION: Die Eigenschaft "style" eines undefinierten oder Nullverweises kann nicht abgerufen werden.
ORIGINAL STACKTRACE:
TypeError: Die Eigenschaft "style" eines undefinierten oder Nullverweises kann nicht abgerufen werden.
at Tooltip.prototype.hide (eval code:76:9)
at Tooltip.prototype.onMouseLeave (eval code:28:13)
at Wrapper_Tooltip.prototype.handleEvent (Function code:63:5)
at View_AppComponent0.prototype.handleEvent_3 (Function code:66:3)
at Anonymous function (eval code:12718:21)
at Anonymous function (eval code:3208:11)
at ZoneDelegate.prototype.invokeTask (https://unpkg.com/zone.js@0.6.25?main=browser:234:17)
at onInvokeTask (eval code:7768:25)
at ZoneDelegate.prototype.invokeTask (https://unpkg.com/zone.js@0.6.25?main=browser:234:17)
at Zone.prototype.runTask (https://unpkg.com/zone.js@0.6.25?main=browser:136:21)
ERROR CONTEXT:
[object Object]
{
[functions]: ,
__proto__: { },
_nodeIndex: 3,
_staticNodeInfo: { },
_tplCol: 0,
_tplRow: 2,
_view: { },
component: null,
componentRenderElement: { },
context: { },
injector: { },
providerTokens: [ ],
references: { },
renderNode: { },
source: "app/app.template.html:2:0",
Symbol(rxSubscriber)_m.73jv94twz6e: undefined
}
SCRIPT5022: Error: Error in app/app.template.html:2:0 caused by: Die Eigenschaft "style" eines undefinierten oder Nullverweises kann nicht abgerufen werden.
Datei: Subscriber.js, Zeile: 227, Spalte: 13
It's a normal IE 11 I use, not a Edge Browser with IE 11 emulation.
-
- Posts: 17
- Joined: 09 Dec 2016, 17:53
It's the same plunker that was posted before: http://plnkr.co/edit/Cd5WqYFXhUEVmVB4BF5H?p=preview
-
- Information
-
Who is online
Users browsing this forum: Google [Bot] and 15 guests