User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030617 Camino/0.7+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030617 Camino/0.7+ Camino fails completely to build a database view (can't get to square one) using phpMyAdmin. Although phpMyAdmin is far from bugfree itself, it works tolerably well in Safari v74 and MS Internet Explorer 5.2.3, but not at all in Camino. Reproducible: Always Steps to Reproduce: 1. Install phpMyAdmin 2.5.1 and Mark Liyanage's PHP library module for Apache 2. Install MySql 4.0.13 from www.mysql.com, then "mysql -p" at Terminal to begin the session 3. Source an sql file to create tables (a small one, ca. 40 Mb expanded, is provided here: http://homepage.mac.com/dcoshel/usda_nutr_db_sr15.sql.gz ) 4. http://yourmachinesrendevous.local/index.php 4a. IF THAT FAILS (probably will ;-), use http://127.0.0.1/index.php 5. Select the nutr_db database using the popup menu top left 6. When that fails, click on Databases in the area about midscreen Actual Results: Zip, zilch, nada. No change. No effect whatever, unlike Safari and MSIE. Note that standard elements of the phpMyAdmin screen are missing (including the small logo top left). Expected Results: It should have displayed a list of the tables contained in mysql; i.e., the mysql database itself, and nutr_db, the USDA Nutrient Database for Standard Release 15. This is square one -- couldn't even select a database using Camino. Mac OS X 10.2.6, X11.app Preview 3, dual usb little white iBook. IMHO, since all the Mac browsers I checked seem to exhibit various minor degrees of these behaviors, which are nevertheless severe enough in Camino to prevent work getting done, there is probably a set of third party interactions involved. It is a major showstopper, though, on Camino.
Dave, could you check two things ? 1) is the problem present when you use Mozilla ? 2) Could you check with a newer Camino nigthly ? Thanks.
WFM with a nightly 2003121403 (0.7+)
Resolving WFM per comment 2. Dave, if you'd like to follow up on the questions in comment 1 and can still reproduce the problem, feel free to reopen.