#4065 (ok 4.1.0-rc1) Can't edit text field, because error dialog is above it

4.0.5
fixed
nobody
None
1
2013-12-12
2013-08-24
dennis1993
No

Hey guys,

I have found a bug.

  1. I create two tables and make a constaint with the ID.
    Code for this:
    CREATE TABLE IF NOT EXISTS categories (
    catID int(11) NOT NULL AUTO_INCREMENT,
    name varchar(25) NOT NULL,
    PRIMARY KEY (catID)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

INSERT INTO categories (catID, name) VALUES
(1, 'Category 1'),
(2, 'Category 2');

CREATE TABLE IF NOT EXISTS items (
itemID int(11) NOT NULL AUTO_INCREMENT,
catID int(11) NOT NULL,
name varchar(25) NOT NULL,
PRIMARY KEY (itemID),
KEY catID (catID)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

INSERT INTO items (itemID, catID, name) VALUES
(1, 1, 'Item 1'),
(2, 1, 'Item 2');

ALTER TABLE items
ADD CONSTRAINT items_ibfk_1 FOREIGN KEY (catID) REFERENCES categories (catID) ON DELETE CASCADE ON UPDATE CASCADE;

  1. I edit an entry. I click on the cell an now I can edit it directly (Screenshot 1)
    I wrote the number 3 in it, buw 1 and 2 are possible (reference to table 1)

  2. If I save it now, I can see two bugs:
    3.1: The query is to long and the dialog to small
    3.2: The dialog is above the text field and I can't edit the wrong value. (Screenshot 2)

The only way: Close the browser and start from beginning. Maybe you can make the dialog above the table or so.

I hope you understand what I mean.

THANKS in advance!

2 Attachments

Discussion

  • Isaac Bennetch

    Isaac Bennetch - 2013-08-27

    Thanks for the thorough report. It does help a lot.

    This might be two bugs plus a feature request (or another bug, depending how you view it, but I think we'll file it as a feature request), as I see it.

    Bug 1: When entering an invalid value in the editor, it keeps trying to insert that value without giving an opportunity to change it.

    Bug 2: The error popup doesn't properly line wrap the SQL statement

    Feature request: The editor should respect foreign key restraints and not try to insert invalid data. Note that there is a dropdown there, so it at least HINTS that you might be doing something wrong.

    It's easier to track each as an individual item rather than grouping them together, so I'll open the other tickets and reference this one.

     
  • dennis1993

    dennis1993 - 2013-08-29

    Ok, thank you very much!

     
  • Marc Delisle

    Marc Delisle - 2013-11-17

    I tested with the current master branch (upcoming 4.1.0-rc1).

    Bug 1: you have an opportunity to change it, with the Edit link which is part of the popup (this was already there in 4.0.9)

    Bug 2: there is now a scroller so that the line wrap is respected

    So, even if it's not perfect, at least you had a way to edit your query and I would consider that this bug is now fixed for 4.1.

     
  • Isaac Bennetch

    Isaac Bennetch - 2013-11-22

    Marc, can we close this as fixed for 4.1?

     
  • Marc Delisle

    Marc Delisle - 2013-11-22
    • summary: Can't edit text field, because error dialog is above it --> (ok 4.1.0-rc1) Can't edit text field, because error dialog is above it
    • status: open --> resolved
    • Priority: 5 --> 1
     
  • Marc Delisle

    Marc Delisle - 2013-12-12
    • Status: resolved --> fixed