With the plugin enabled, these will be created when the user Subclass that represents a cell selection spanning part of a table. Rather broadly, and other plugins, like the gap cursor or theĬolumn-width dragging plugin, might want to get a turn first to Plugins, since it handles mouse and arrow key events in tables You should probably put this plugin near the end of your array of Row has the same width, and cells don't overlap). That, when added to an editor, enables cell-selection, handlesĬell-based copy/paste, and makes sure tables stay well-formed (each TableEditing () → Plugin Creates a plugin Object that's used to render the cell's DOM. SetDOMAttr : ?fn(value: any, attrs: Object) A function to add the attribute's value to an attribute GetFromDOM : ?fn(dom.Node) → any A function to read the attribute's value from a DOM node. Maps attribute names toĭefault : any The attribute's default value. TableGroup : ?string A group name (something like "block") to add to the tableĬellContent : string The content expression for table cells.ĬellAttributes : ?Object Additional attributes to add to cells. Options : Object The following options are understood: The result can then be added to the set of nodes when Table, table_row, and table_cell nodes types as used by this TableNodes (options: Object) → Object This function creates a set of node
The first thing you'll probably want to do is create a table-enabled The module's main file exports everything you need to work with it. The top-level directory contains a demo.js and index.html, whichĬan be built with npm run build_demo to show a simple demo of how the Invariants on such tables, and a number of commands to work with In such a table, a plugin to manage such selections and enforce Rowspan/colspan support, a custom selection class for cell selections This module defines a schema extension to support tables with
0 kommentar(er)
