You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original install method (e.g. download page, yum, from source, etc.):
apt
Describe the bug:
I'm noting that renderComplete seems to fire far too frequently for Discover saved searches. It seems to fire as each row is rendered, rather than when rendering completes.
Steps to reproduce:
Load a visualization that includes a Discover search
Load test code via the browser console:
$("doc-table.panel-content").on("renderComplete", function(){
console.log("renderComplete Ran: " + new Date().getTime() );
});
Use the tables paging buttons to force a refresh
Observe ~101 lines logged to the browser Console
Using an alert() in the test pauses things with each iteration that seems to show it occurring as each row is rendered
Expected behavior:
renderComplete would fire once when all table rows had completed rendering.
The text was updated successfully, but these errors were encountered:
For me the main issue I have is that I can't use renderComplete to know when things are complete, since they won't be the first time it fires, and there is no way to know if the 20th or 50th time it's run will be the last.
This would be likely to cause performance issues for some scripts, or probably more critically, repeated DOM changes for things that modify the DOM in renderComplete.
Kibana version:
6.5.2
Elasticsearch version:
6.5.2
Server OS version:
Ubuntu 16.04.05
Browser version:
Firefox
Browser OS version:
Windows 10
Original install method (e.g. download page, yum, from source, etc.):
apt
Describe the bug:
I'm noting that renderComplete seems to fire far too frequently for Discover saved searches. It seems to fire as each row is rendered, rather than when rendering completes.
Steps to reproduce:
Using an alert() in the test pauses things with each iteration that seems to show it occurring as each row is rendered
Expected behavior:
renderComplete would fire once when all table rows had completed rendering.
The text was updated successfully, but these errors were encountered: