Closed
Bug 185939
Opened 23 years ago
Closed 22 years ago
phpMyAdmin blank areas where expanding list not collapsing
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: christiank, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Running any installation of phpMyAdmin 2.1.0 (eg on MySQL 3.22.32) the
left-frame expandable list always appears incorrectly in Phoenix but always
appears correctly in MSIEv5. The subcategories (table names) appear and
dissappear correctly when clicking on a category (database name), but they fail
to collapse and save space as they do on IE. As a result a lot of blank space
remains and the left frame scrolls and is a lot longer than it should be.
Reproducible: Always
Steps to Reproduce:
1. Install phpMyAdmin on any mysql server
2. Open the main page for this tool
3. Try expanding and collapsing the database names on the left
Actual Results:
The table names disappear and a blank space remains.
Expected Results:
The other names beneath where I clicked should be scrolling up to fill the void.
Any theme. No crash. WinNT4 SP6 Intel. I think this is a Javascript or DOM
issue, but I did not find 'phpMyAdmin' on a keyword search so I did not know
where to file this (my personal apologies to anyone who has to find an old bug
to file this under).
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
phpMyAdmin 2.3.2
I would check out http://www.phpmyadmin.net/ and d/l a newer version. They must
have fixed this in a newer version. I'm new to phpMyAdmin but to get a tree
layout in my version set $cfg['LeftFrameLight'] = FALSE; in config.inc.php.
NOTE that I used Mozilla 1.3a and not Phoenix as you never mentioned if MOzilla
worked.
Thanks for the tip about the tree view.
This bug should be closed.
Comment 2•22 years ago
|
||
FIXED per #1.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•