(ok 2.11.0-rc2) dropdown instead of input when editing

Logged In: YES
user_id=210714
Originator: NO

Cannot reproduce with 2.10.2 or trunk. When it happens, please paste the HTML output here.

Logged In: YES
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

example source of the bad.page.html

Logged In: YES
user_id=1383652
Originator: YES

it happend again:
http://pma.cihar.com/trunk-config/tbl_change.php?db=test&table=test1

-- Database: `test`
-- Table structure for table `test1`

CREATE TABLE IF NOT EXISTS `test1` (
`OS` varchar(20) NOT NULL,
`Mascot` varchar(20) NOT NULL,
`Price` float NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

nothing unusual...

the html.page attached (only css missing)...
File Added: bug1751553.tbl_change.php.zip

Logged In: YES
user_id=1383652
Originator: YES

miraculously today it's working again on the demo server - inspite of no changes in the code ...

int example from cihar.com

Logged In: YES
user_id=1383652
Originator: YES

again you can see some weird input form on the demo server:
this time a integer field is effected ...
http://pma.cihar.com/trunk-config/tbl_structure.php?db=test&table=utf8_test
when you click on insert (same issue on STABLE, tested with SeaMonkey-Gecko and IE6)

CREATE TABLE IF NOT EXISTS `utf8_test` (
`id` int(11) NOT NULL,
`id_test` int(11) NOT NULL,
`field1` varchar(256) character set utf8 collate utf8_unicode_ci NOT NULL,
`field2` varchar(256) character set utf8 collate utf8_unicode_ci NOT NULL,
PRIMARY KEY (`id`),
KEY `id_test` (`id_test`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

If I create a new db (test_1751553 on demo) and insert this table everything works as exspected.

File Added: bug1751553.int.htm.zip

Logged In: YES
user_id=210714
Originator: NO

I can reproduce this problem if I define a relation from id_test to id and the table is empty. An empty drop-down is displayed. So, sometimes when you tested, the relation was there, sometimes it wasn't?

Logged In: YES
user_id=1383652
Originator: YES

sorry Marc,
I can't remember exactly the circumstances nor could I reproduce it,
I just stumbled about it randomly when I visited the db "test" on the demo server. I never monitored any relation involved until now. It's strange that nobody else noticed this issue. I'm glad you were able to reproduce it.