Mateusz Paprocki

Thanks. > I added the `plat: safari` and `type: bug` labels but I'm not entirely sure how to title and label this issue. That's a good start.

This is currently being worked on (in a broader setting) (scheduled for 2.3 release).

There is none.

> I self-assigned the issue to indicate that I had already begun working on a PR. I started working on this before you self-assigned. Also in my view, changes in...

I've been considering implementing the following for a while: * allow multiple formatters to be specified/chained (equivalent to jinja's chains/pipelines), i.e. `@{field}{custom | safe}`, while preserving backwards compatibility * allow...

The default value is 1.0, so setting the property to the same value is a no-op. We need to mark such properties as "dirty", so that when applying a theme,...

I don't see this bug as a theming issue, but as a simple bokeh doesn't respect user inputs type of issue.

This is actually somewhat implemented in PR #13279 as "shapes" API. This includes marker shape that acts like a scalar equivalent of marker glyph.

@bryevdv, what the resolution for this, `noaction`?

The biggest issue with consolidation is that `CustomJS` requires `async`, but not all contexts where other custom JS models are used allow that.