SEHI L'YI

> This is similar to part of the discussion in #579, and I'd argue for a similar reason they are not necessary. I assume the custom fields will be either...

The last track (`.bed`) combined with the use of custom assembly (`assembly: [[a, N]]`) is making it slow. When I uncomment them, it's okay.

Hmm, this seems to be a much more substantial update than I expected. Would need to spend some time later.

I think a combination of using [`hgRef.current.getLocation()`](https://docs.higlass.io/javascript_api.html#getLocation) and `gosRef.current.zoomTo()` can allow implementing zoom in and out buttons. One thing we can support in the API is something like `zoomIn()` and...

Partly supported in #722. We can additionally support `language` and store two specs separately, i.e., JSON and JS codes. See below: --- I am wondering will it make sense to...

I think this can be a useful addition to the grammar. One limitation would be that the _expression_ is expressed in a string format, so we cannot provide auto-completion and...

Reproducible using the following spec: ```js { "arrangement": "vertical", "views": [ { "static": true, "layout": "circular", "alignment": "stack", // "xDomain": { "chromosome": "5" }, "tracks": [ { "alignment": "overlay", "data":...

Hi Zhen, we are planning to support other assemblies as well for the public data. In the meantime, you could use the data that is supported by the HiGlass server:...

Great to hear that you found a way to address the issue. The CSS class names of the tooltip are the following, so you can override the z-index of the...

Hi Zhen, You could use the `reactive` rendering for this ([Complete Code](https://github.com/gosling-lang/gosling-react/pull/4)).  One limitation depending on your use case might be that upon the resize, the zoom level...