Explore tooltip integration options:

1. when under x series, we can use svg and then put a tooltip listener on each line; when over x series, no tooltip.
2. Use interaction space to get "closest" line to the cursor. Interaction space would have to go UNDER the axis drawing space to allow for axis drag and brush capabilities.

tooltip should display either point on the line at axis closest to the cursor or all axes values for that line

Need to see if either method is feasible performance and interaction wise.

We need to support multiple categories (assets) where each set of lines get a different color based on category.

The series in the PC chart should be based on the extents chosen on the navigator.

1. make sure the lines respond to changes to the navigator selectedDomain
2. upgrade px-vis-brush used in the navigator: brush rect.overlay need to have a gradient from 20%-100%. (this gradient will then match the gradient given to the lines)

Thickness of axis on Safari 9 is thicker than other browsers. And renders differently on different displays.

(See Wade for details.)

Need to add an optional register. It just needs to display the axis names, not any values. You should be able to mute an axis via the register and it will remove the corresponding axis from the chart. Unmuteing the axis via the register will then return it to the chart.

Can use $chart.dimensions.

Either document this or create a return function to get it. Check with Jum that muting / unmuting should still be in the list.

Check out the truncation done in register

If we have a commonAxis, the text on the first axis is visible, the others have an on-hover functionality. If I drag the first axis to the middle, the styles do not update.

The problem is that the order on the dom is still the same, so it believes it to still be the first axis. Need to look into how to get the ordinal drawn order...

See px-vis-multi-axis for code

Need to calc a conservative width / axis, if we have too many axes, then rotate the label 90 degrees per spec.

We need to check our error handling with missing data:
Eg: Line has one blank value on an axis - it should leave a break

axis trailing garbage when we remove axis

Move an axis and it will sometimes not snap into position

Dev should be able to specify if the chart draws using max data extents or (current behavior) individual extents for each axis.

Per spec, the axes values labels will be hidden; on axis hover, they should appear and be grey

Does not need to be dynamic, but would be a big plus.

Hi,
We tried passing chart-extents="{"x": [0,100],"y": [5,50]}" in the px-vis-parallel-coordinates, however we are not able to see any changes in the output. Could you please confirm whether this functionality will work in this component?

Also, confirm is it "dynaimc" or "dynamic"? as per specification it is like below.
chartExtents
Object notifies
Developer set chart extents for the chart. The chart will draw to whatever values are specified in the chartExtents.

{
"x": [0,100],
"y": [5,50],
}
To force the chart to calculate based on data, use "dynamic".

{
"x": [0,"dynaimc"],
"y": [-10,"dynaimc"],
}
For an ordinal dataset, chart extents can be set like this:

{
"x": ['low','medium','high'],
"y": [5,50],
}

when first loading the page 2 drawing occurs after the labels at the bottom rotate. the first darwing is not cleared, making the chart false

Need use the dark color set. Probably easiest to just add n to the colorseriesorder getter to start at the dark colorset.

Need to also add 20-100% opacity based on time

Make sure that when setting "axes" and loading data later on the chart loads properly

Experiment with progressive rendering and see if we can get it to work well.

Current stub takes too long as it only draws 1 line every "1ms". Should try to make it draw larger sets of data over a timeframe.

Also look into making not do that for the first render, but only for subsequent renders.