unexpected behaviour when editing content of a cell

[cldougl]

when editing content of a cell 1 click should highlight content and overwrite all content
clicking a second time should place the cursor and insert the edit at the cursor
at this time I'm seeing the edit get prepended rather than overwriting or inserting at cursor in the python example (both on master and develop branches)

working as expected in js example (ie npm run build.watch visit: http://127.0.0.1:8080/ )
not working on master nor develop for configurable options example (gunicorn index:server -b localhost:8050 --reload http://127.0.0.1:8050/editor-with-configurable-options)
working on develop (example not on master yet :) ) for dataframe updating example (gunicorn index:server -b localhost:8050 --reload http://127.0.0.1:8050/dataframe-updating-graph-fe)

[valentijnnieman]

If I boil down the configurable options example to something simpler, it works fine:

app.layout = html.Div(
    className="row",
    children=[
        html.Div(
            className="four columns",
            children=dash_table.Table(
                id='table',
                columns=[{"name": i, "id": i} for i in df.columns],
                dataframe=rows,
                editable=True,
                sorting=True,
                sorting_type="single",
                sorting_treat_empty_string_as_none=True,
                row_selectable="single",
                pagination_mode="fe",
                n_fixed_rows=0,
                n_fixed_columns=0
            ),
        ),
        html.Div(
            id='output'
        )
    ],
)

@app.callback(
    Output('output', "children"),
    [
        Input('table', "derived_virtual_dataframe"),
        Input("table", "selected_rows"),
    ],
)
def simple_callback(df, rows):
    return rows

The main difference is that in the configurable options example, the table itself is coming from a callback, i.e. a callback is getting all the dropdown inputs (options), and is returning a table to an output container. The second callback is then getting inputs based upon an entirely new table (set to AVAILABLE_PROPERTIES). I feel the error lies somewhere in here - will investigate more, just wanted to write down my thoughts :)

[valentijnnieman]

What's interesting is that I can't seem to recreate a simplified example where the table is being generated in a callback, and returned to some sort of container's output. I don't really understand how it works in the app_editor_with_configurable_options.py app, but I did notice this juicy front end error coming from dash-renderer's bundle.js:

The culprit of that error is the callback on line 132:

@app.callback(
    Output("output", "children"),
    [Input(__name__, prop) for prop in AVAILABLE_PROPERTIES],
)
def display_propeties(*args):