Some people seem to be having lots of problems accessing the build logs from Tinderbox. Mostly these seem to be cause by the dialog that pops up when you click on one of the links (l, L C), in that the dialog goes away before you have a change to click one of the links in the dialog.
I'd rather not get rid of the dialog because it does provide one useful bit of information: the time it took for that cycle. Here are some of the things I know to work around the vanishing dialog box problem. First ways you can bypass the dialog completely: In Firefox I can middle click a link to open it in a tab (requires 3 button mouse, is also configurable in Firefox). Alternatively on Linux you can simulate the middle click by pressing left and right button simultaneously. In Firefox I can drag and drop a link to a tab header or an empty spot on the tab bar to open the link in a tab. Install noscript extension to Firefox and have JS disabled on Tinderbox page. This results in clicks on those links always going directly to the log. Information on how to deal with the dialog: The dialog goes away if you: 1) Mouse over any link outside of the dialog 2) Mouse over the close link in the top right corner of the dialog So if you avoid those actions you should be able to click one of the links in the dialog itself. I've heard some reports that some browser+platform combination makes the dialog go away as soon as you move the mouse, no matter where. Some people have also reported the dialog going away no matter what they do, regardless of platform and browser. Do you know a platform+browser combination that makes using the dialog hard, or where there are no workarounds to bypass the dialog? Still, the dialog is pretty flaky so it would be nice to fix it. Any volunteers? There have been a few of proposals on how to fix this: * Provide a new link that pops up the dialog, and change the old links to go directly to the log * Write the cycle time in the cell itself and disable the dialog completely * Change the dialog code so that it goes away only when the close "button" is clicked. Other ideas on how to deal with this? -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
