##// 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:

r16912:30744239
r20621:f936f880
Show More
completer.less
25 lines | 501 B | text/x-less | LessCssLexer
.completions {
position: absolute;
z-index: 10;
overflow: hidden;
border: 1px solid @border_color;
.corner-all;
.box-shadow(0px 6px 10px -1px #adadad);
}
.completions select {
background: white;
outline: none;
border: none;
padding: 0px;
margin: 0px;
overflow: auto;
font-family: @font-family-monospace;
font-size: 110%;
color: @text-color;
width: auto;
}
.completions select option.context {
color: darken(@brand-primary, 10%);
}