Angular Data GridCell Editors
angular logo

Create your own cell editor by providing a cell editor component.

The example below shows a few cell editors in action.

  • The Doubling Cell Editor will double a given input and reject values over a 1000
  • The Mood Cell Editor illustrates a slightly more complicated editor with values changed depending on the smiley chosen
  • The Numeric Cell Editor illustrates a slightly more complicated numeric editor to the Doubling editor, with increased input validation

Implementing a Cell Editor Component

The interface for the cell editor component is as follows:

interface ICellEditorAngularComp {
  // Mandatory - Params for rendering this component. 
  agInit(params: ICellEditorParams): void;

  // Return the final value - called by the grid once after editing is complete
  getValue(): TValue | null | undefined;

  // Optional: Gets called with the latest cell editor params every time they update
  refresh?(params: ICellEditorParams<any, TValue>): void;

  // Optional: A hook to perform any necessary operation just after the GUI for this component has been rendered on the screen.
  // This method is called each time the edit component is activated.
  // This is useful for any logic that requires attachment before executing, such as putting focus on a particular DOM element.
  afterGuiAttached?(): void;

  // Optional: Gets called once after initialised. If you return true, the editor will
  // appear in a popup, so is not constrained to the boundaries of the cell.
  // This is great if you want to, for example, provide you own custom dropdown list
  // for selection. Default is false (ie if you don't provide the method).
  isPopup?(): boolean;

  // Optional: Gets called once, only if isPopup() returns true. Return "over" if the popup
  // should cover the cell, or "under" if it should be positioned below leaving the
  // cell value visible. If this method is not present, the default is "over".
  getPopupPosition?(): 'over' | 'under' | undefined;

  // Optional: Gets called once after initialised. If you return true, the editor will not be
  // used and the grid will continue editing. Use this to make a decision on editing
  // inside the init() function, eg maybe you want to only start editing if the user
  // hits a numeric key, but not a letter, if the editor is for numbers.
  isCancelBeforeStart?(): boolean;

  // Optional: Gets called once after editing is complete. If your return true, then the new
  // value will not be used. The editing will have no impact on the record. Use this
  // if you do not want a new value from your gui, i.e. you want to cancel the editing.
  isCancelAfterEnd?(): boolean;

  // Optional: If doing full line edit, then gets called when focus should be put into the editor
  focusIn?(): void;

  // Optional: If doing full line edit, then gets called when focus is leaving the editor
  focusOut?(): void;


The interface for the params argument passed to agInit is ICellEditorParams:


Properties available on the ICellEditorParams<TData = any, TValue = any, TContext = any> interface.

Registering Cell Editors with Columns

See the section registering custom components for details on registering and using custom cell editors.

Complementing Cell Editor Params

As with cell renderers, cell editors can also be provided with additional parameters. Do this using cellEditorParams as in the following example which will pass 'Ireland' as the 'country' parameter:

colDef = {
    cellEditor: MyCellEditor,    
    cellEditorParams: {
        // make "country" value available to cell editor
        country: 'Ireland'
    // ...other props

Configure Popup

Configure that a Custom Cell Editor is in a popup in one of the following ways:

  1. Implement the isPopup() method on the Custom Cell Editor and return true.
  2. Specify cellEditorPopup=true on the Column Definition.
colDef = {
    cellEditorPopup: true,
    // ...other props

Configure Popup Position

By default Popup Editors appear over the editing Cell. It is also possible to have the Cell Editor appear below the Cell, so the user can see the Cell contents while editing.

Configure the Popup Editor to appear below the Cell in one of the following ways:

  1. Implement the getPopupPosition() method on the Custom Cell Editor and return under.
  2. Specify cellEditorPopupPosition='under' on the Column Definition.
colDef = {
    cellEditorPopupPosition: 'under',
    // ...other props

Keyboard Navigation While Editing

If you provide a cell editor, you may wish to disable some of the grids keyboard navigation. For example, if you are providing a simple text editor, you may wish the grid to do nothing when you press the right and left arrows (the default is the grid will move to the next / previous cell) as you may want the right and left arrows to move the cursor inside your editor. In other cell editors, you may wish the grid to behave as normal.

Because different cell editors will have different requirements on what the grid does, it is up to the cell editor to decide which event it wants the grid to handle and which it does not.

You have two options to stop the grid from doing it's default action on certain key events:

  1. Stop propagation of the event to the grid in the cell editor.
  2. Tell the grid to do nothing via the colDef.suppressKeyEvent() callback.

Option 1 - Stop Propagation

If you don't want the grid to act on an event, call event.stopPropagation(). The advantage of this method is that your cell editor takes care of everything, good for creating reusable cell editors.

The follow code snippet is one you could include for a simple text editor, which would stop the grid from doing navigation.

const KEY_LEFT = 'ArrowLeft';
const KEY_UP = 'ArrowUp';
const KEY_RIGHT = 'ArrowRight';
const KEY_DOWN = 'ArrowDown';
const KEY_PAGE_UP = 'PageUp';
const KEY_PAGE_DOWN = 'PageDown';
const KEY_PAGE_HOME = 'Home';
const KEY_PAGE_END = 'End';

    selector: 'my-editor',
    template: `<input (keydown)="onKeyDown($event)" of input/>`
export class MyCellEditor implements ICellEditorAngularComp {
    /* Component Editor Lifecycle method */
    agInit(params: ICellEditorParams) {
        this.params = params;

    onKeyDown(event) {
       const key = event.key;

        const isNavigationKey = key === KEY_LEFT ||
           key === KEY_RIGHT ||
           key === KEY_UP ||
           key === KEY_DOWN ||
           key === KEY_PAGE_DOWN ||
           key === KEY_PAGE_UP ||
           key === KEY_PAGE_HOME ||
           key === KEY_PAGE_END;

           if (isNavigationKey) {
               // this stops the grid from receiving the event and executing keyboard navigation
    } of the component

Option 2 - Suppress Keyboard Event

If you implement colDef.suppressKeyboardEvent(), you can tell the grid which events you want process and which not. The advantage of this method of the previous method is it takes the responsibility out of the cell editor and into the column definition. So if you are using a reusable, or third party, cell editor, and the editor doesn't have this logic in it, you can add the logic via configuration.

const KEY_UP = 'ArrowUp';
const KEY_DOWN = 'ArrowDown';

    selector: 'my-grid',
    template: `
       of the component...>
export class AppComponent {
    private columnDefs = [
                headerName: "Value Column",
                field: "value",
                suppressKeyboardEvent: params => {
                    console.log('cell is editing: ' + params.editing);
                    console.log('keyboard event:', params.event);
                    // return true (to suppress) if editing and user hit up/down keys
                    const key = params.event.key;
                    const gridShouldDoNothing = params.editing && (key === KEY_UP || key === KEY_DOWN);
                    return gridShouldDoNothing;
    ] of the component...

Cell Editing Example

The example below illustrates:

  • 'Gender' column uses a Component cell editor that allows choices via a 'richSelect' (AG Grid Enterprise only), with values supplied by complementing the editor parameters.
  • 'Age' column uses a Component cell editor that allows simple integer input only.
  • 'Mood' column uses a custom Component cell editor and renderer that allows choice of mood based on image selection.
  • 'Address' column uses a Component cell editor that allows input of multiline text via a 'largeText'. ⇥ Tab and ⎋ Esc (amongst others) will exit editing in this field, ⇧ Shift+↵ Enter will allow newlines.
  • 'Country' columns shows using 'richSelect' for a complex object - the cell renderer takes care of only rendering the country name.

Accessing Cell Editor Instances

After the grid has created an instance of a cell editor for a cell it is possible to access that instance. This is useful if you want to call a method that you provide on the cell editor that has nothing to do with the operation of the grid. Accessing cell editors is done using the grid API getCellEditorInstances(params).

If you are doing normal editing, then only one cell is editable at any given time. For this reason if you call getCellEditorInstances() with no params, it will return back the editing cell's editor if a cell is editing, or an empty list if no cell is editing.

An example of calling getCellEditorInstances() is as follows:

const instances = api.getCellEditorInstances(params);
if (instances.length > 0) {
    const instance = instances[0];

The example below shows using getCellEditorInstances. The following can be noted:

  • All cells are editable.
  • First Name and Last Name use the default editor.
  • All other columns use the provided MySimpleCellEditor editor.
  • The example sets an interval to print information from the active cell editor. There are three results: 1) No editing 2) Editing with default cell renderer and 3) editing with the custom cell editor. All results are printed to the developer console.