##// END OF EJS Templates
Handle kernel messages synchronously...
Handle kernel messages synchronously A problem can happen when two messages come in for different comms, where the second depends on the first (for example, the first might be a message setting the state of a widget, and the second triggering a view creation for the widget). Since comm message queues are independent of each other, the second message could be executed before the first message. This exposes a more fundamental assumption users are likely to have that messages from python are processed synchronously. Thanks to @dmadeka for reporting an error that led to discovering this issue.

File last commit:

r19298:d8390523
r20621:f936f880
Show More
notificationwidget.less
20 lines | 348 B | text/x-less | LessCssLexer
.notification_widget {
color: @navbar-default-link-color;
z-index: 10;
background: @notification_widget_bg;
.btn-default();
}
.notification_widget.warning {
.btn-warning();
}
.notification_widget.success {
.btn-success();
}
.notification_widget.info {
.btn-info();
}
.notification_widget.danger {
.btn-danger();
}