Kanit Wongsuphasawat

They are all similar but slightly different: - #3153 uses `domain` in the spec, this issue uses `sort`. - #4932 specifies `sort` in all layers, this issue specifies only one.

I think the solution for this particular one is to consider `sort` as one of the component (or part of the scale component) that gets respected when we later derive...

If we extend Vega domain sort to support either (a) sorting by a calculated field based on each unique value (b) custom sort order. Then such domain `sort` could be...

@ben741 - try adding `"stack": false` to x for now (`"x": {"field": "val", "type": "quantitative", "stack": false}`). The underlying issue is that bar with color encoding is stacked by default...

As discussed on slack, this sounds good. Though we need to make sure that this doesn't lead to a regression somewhere else. (For example, while we haven't fixed nested facet...

(Note that we can already use path to draw ellipse, but for annotation purpose, having a standard mark will be way more convenient.

Fixing this - [x] for raw plot is pretty straightforward -- just sort by the sort field of the dimension channel instead of the dimension channel's field. (Fixed in #1523)...

> for aggregate plot, this can be tricky as they require adding more fields to the aggregate transform to make sure we have the required field. To be precise, this...

The [small example case](https://github.com/vega/vega-lite/issues/1520#issuecomment-493760240) will be fixed in https://github.com/vega/vega-lite/pull/5089. But we still have the aggregate plot case unfixed. I think that case is P3 though.

The easiest way is to the set the scale [domain](https://vega.github.io/vega-lite/docs/scale.html#domain) of the x and y axes to the same values.