mlms13 / fancygrid Goto Github PK

If you specify a height (in the CSS) greater than the height of your table, there is no way to put a border around only the table (or make the container shrink to only the required space, etc). max-height isn't an option, because then all of the inner items are treated as 0 height, and it doesn't know how to absolutely position any of the cell heights.

• columns
• rows
• contentWidth
• contentHeight

Classes like row have screwy margins, thanks to Bootstrap. It's not hard to imagine that left, right, view, column, and cell are also styled globally by various frameworks. Other Fancy* libraries generally prefix class names with some fancy-specific letters, which will help us avoid conflicts.

This is for the new selection code in @fponticelli's fork.

I'm seeing this error in the store data hub table when navigating around with the keyboard:

bundle.js:2061 Uncaught RangeError: Maximum call stack size exceeded
    at fancy_Grid.vOffset (bundle.js:2061)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)
    at fancy_Grid.vOffset (bundle.js:2068)

Here is the section of compiled .js code referenced above:

	,assignVOffset: function(f) {
		var _gthis = this;
		if(null != f) {
			return f;
		}
		var cache = new fancy_core_IntCache();
		this.caches.push(cache);
		return function(row) { // LINE 2061
			if(row == 0) {
				return 0;
			}
			if(cache.cache[row] != null) {
				return cache.cache[row];
			}
			var v = _gthis.vOffset(row - 1) + _gthis.vSize(row - 1); // ERROR HERE?
			cache.cache[row] = v;
			return v;
		};
	}

Uncaught NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

This happens in the assignHSize function.

In our app, we have an initial state with only one column of data. Those cells have a width of 100%. When the browser width is increased, we snap to a different breakpoint, and the table is given more width, however the 100% cells still have a fixed width (set by FancyGrid) that reflects their width in the smaller table.