Mateusz Paprocki

There are 4 integration test failures, but only one seems to be actually breaking (other seem trivial): Bug ⇒ in issue #12584 ⇒ doesn't allow auto-completion to work correctly in...

Sure, but I don't see any pressure for this issue to be resolved now, especially given the state of the underlying implementation. If anything, it would be nice if you...

> In the longer term, I believe the plan is to move some elements like axes to DOM rendering, in which case the browser can be responsible for text wrapping....

Indeed, when all tools are disabled, panning over a plot should result in browser's default behavior, but currently nothing happens. Most likely a regression introduced in the recent redesign of...

We currently set `touch-action: none`, which completely prevents browser from handling touch events. What we need to do, is to manipulate `touch-action` depending on currently active tools and gestures they...

Let's start a new issue for this. For me hover works, but that's on a device with a pen.

> The number of roles you added looks substantial! I just copied whatever I found on MDN, not that I'm using all of them. Do you know if the ones...

@philippjfr, who is supposed to review/approve this kind of work?

I disagree with closing this as a duplicate of #14095. This behavior is not limited to `Line` glyph (e.g. applies to `Scatter` as well). No amount of documentation can fix...

This happens because two glyph renderers are connected by a data source. During inspection (hover), inspection indices change on the data source, which triggers an update mechanism for all connected...