Bug in the XML Grid example - Ext JS

# 2 03-06-2007, 11:55 AM

Quote:

Originally Posted by liotrox

...
1. Try to lock all columns: the whole grid will disappear
2. Try to resize columns trying to put a very very small size....
Angelo

On bug 1. What steps to recreate this issue, what message?

On bug 2. Do you mean ...
A) when you resize to a small size you get an error
or
b) when you try to resize it changes to a small size (and if so - what goes small)?

In reference to (A) above - I was able to recreate a similar bug in I.E. and Firefox while trying to make it small but only when mousing off the screen (why it was hard to re-create at first).

How to recreate this bug (may be a known bug, I am very very new).
---------------------------------------------------------------------------------------------
- Open a grid example, such as the XML GRID referenced in this thread.
- Size the first column small but keep going off the grid and release mouse off grid.
- When you let go you will see errors or bugs. In i.e. i got an error message and in both cases the column resizes incorrectly.

Note: I get this same error in all examples including the paging one.

Hope this helps at least clarify what your question was and how I was able to recreate some bugs.

Great tool - minor bugs

# 3 03-06-2007, 03:58 PM

To create the bug 1:
- Lock all the columns one-by-one using the context menu of the column header (right-click)
once you lock the last column the grid disappear.

To create the bug 2:
- Resize the column 'title' as smallest you can but dragging the mouse out of the column title (i.e. move the mouse till you reach the column author header). You will see the grid headers not correctly rendered. The bug is 'worst' in case you have some locked columns.

Angelo

# 4 03-06-2007, 05:35 PM

I am just a new guy that was trying to understand your issue I am not an official "dude" here. Just replied to help share some bugs I found, so take my comments with a grain of salt.

I found some bugs when all columns are locked as well, mainly dom related errors.

I know this sounds stupid but I'll throw it out anyway ... A simple workaround would be to check all columns and not allow the last one to be locked (since it makes no since to do so anyway and all the issues seems to occur when this happens).

Just a thought

# 5 03-06-2007, 08:12 PM

All of these are fixed in the trunk. Thanks guys.