Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#5054 closed defect (fixed)

Grid c.editor has no properties after trying to resize a header

Reported by: guest Owned by: sorvell
Priority: high Milestone: 1.0.1
Component: DojoX Grid Version: 1.0
Keywords: Grid c.editor resize header Cc:
Blocked By: Blocking:


I do not know how you rate your severity levels, but this problem causes the dojo grid to error out and, to the user of the grid, appears to "destroy" their grid data. I flagged it critical because of this.

You can use your test located here as an example of this problem:

You can recreate the error "c.editor has no properties" when attempting to resize a grid header after double clicking on a row. I have had this issue when reloading data from a datastore, but had no way to give you an example without giving you my code until I found this issue also resides when resizing a header and not just re setting the grid model.

Steps to recreate: 1) Double click on row 2 (any row will work, but 2 is this example) 2) Make sure that the double click highlighted the row "green" as if it was going to be edited 3) Resize any of the headers

The error should show in firebug as "c.editor has no properties". In addition to the error, everything after the selection you made will not render in the grid and it will appear to be missing everything past that row.

Change History (5)

comment:1 Changed 15 years ago by sjmiles

Resolution: fixed
Status: newclosed


Grid should not put editor-less cells in edit mode. Also (likely redundant) protection against referencing null c.editor. fixes #5054

comment:2 Changed 15 years ago by Adam Peller

Resolution: fixed
Status: closedreopened

has to go in 1.0 branch as well

comment:3 Changed 15 years ago by Adam Peller

Resolution: fixed
Status: reopenedclosed

Fixed on 1.0 branch also: [11460]

comment:4 Changed 15 years ago by Adam Peller

oops. meant [11461]

comment:5 Changed 15 years ago by Adam Peller

(In [11468]) mirror checkin [11460] in 1.0 branch. Refs #5054

Note: See TracTickets for help on using tickets.