BTW, I've tried disabling all my addons to see if that made any difference - it didn't.
On Wed, Jan 19, 2011 at 8:29 AM, Tikkanz <[email protected]> wrote: > Here are my observations - they don't appear to match up with yours. > > I've now tested on: > * 32-bit Win7 Firefox 4.0 beta9 > * 64-bit Ubuntu 10.04 Firefox 3.6.13 > * 64-bit Ubuntu Chromium 8.0.552.224 > > I've only had issues with Firefox on Ubuntu. > > It only affects links (menus or links on page) on the jijx page. Menu > links and links on the page on other JHS pages (e.g. help, jal, jfile > etc) all respond as expected to middle-click. > > Only middle-clicking on a link gives no response. Left- & > right-clicking work as expected. > > Seems to be an odd one! > > On Wed, Jan 19, 2011 at 4:44 AM, Eric Iverson <[email protected]> > wrote: >> Ric, >> >> I think I understand problem with menu vs middle button. >> >> First I would like to confirm the problem. My observations are: >> 1. happens on all page links (jijx, jijs,...) >> 2. happens on all buttons (left, middle, right) >> 3. depends on how fast you click and release >> 4. happens with Chrome,FF >> 5, does not happen with IE >> 6. does NOT happen with links on the page (such as from open'~temp/f.ijs') >> >> A mouse down sets a timer that kills the drop down menu when it triggers. >> Press and hold a mouse button on a link menu item and release after it after >> the menu disappears. >> >> My guess is that you noticed this with a middle mouse button because being a >> bit unfamiliar ones fingers are just a tiny bit slower. Experiment with >> deliberately fast or slow clicks to verify the theory. >> >> The hardest part in browser menu management is to get it to hide when it >> should. An adequate fix may be as simple making the timer timeout just a bit >> longer. Changing mouse up and down actions is messy because this is an area >> where browsers differ and I have tried to avoid browser detection in the >> javascript as much as possible. Differences in mouse down/up is why IE >> doesn't have the problem. >> >> Does the above match your observations? If so, I'll put out a simple kludge >> fix that just increases the timeout a bit. >> >> >> On Mon, Jan 17, 2011 at 6:42 PM, Tikkanz <[email protected]> wrote: >> >>> More investigation reveals that it is only the jijx page that seems to >>> be affected. Middle-click on links on other pages (including the menu >>> links) seem to work as I expect. The jijx page seems to being treated >>> differently. >>> >>> On Tue, Jan 18, 2011 at 12:04 PM, Eric Iverson <[email protected]> >>> wrote: >>> > For me the middle button in FF opens in a new tab in all cases. I don't >>> > think this is anything that JHS has any control over. What happens with >>> > normal links on normal pages? Perhaps your FF config has changed. >>> > >>> > I get the same new tab behavior in Chrome. >>> > >>> > Note that the middle button opens the link in a new tab, but leaves focus >>> on >>> > the current tab. This is often not what you want so ctrl+shift+click is >>> > still your best bet. >>> > >>> > Not using javascript to open a new tab is not a security concern. At >>> least >>> > not for me or for JHS. But the web politically correct police say one >>> > shouldn't do this. And my understanding is that many users have >>> javascript >>> > configured to prevent it. I think this remains an open question that may >>> be >>> > resolved in pacman updates after the official release. >>> > >>> > On Mon, Jan 17, 2011 at 5:46 PM, Tikkanz <[email protected]> wrote: >>> > >>> >> Using Firefox, when I middle-click (scroll-button-click) on a link, >>> >> the link usually opens in a new tab. >>> >> >>> >> From memory that used to work in JHS, but now doesn't seem to do >>> >> anything. So for example middle-clicking on the link|jfile menu item >>> >> should open the jfile page in a new tab, but currently doesn't appear >>> >> to do anything. >>> >> >>> >> The link generated by the open command also suffers from this same >>> >> behaviour. Right-clicking on the link and choosing "Open Link in New >>> >> Tab" works fine. >>> >> >>> >> (FWIW I would prefer the open command to just open the file in a new >>> >> tab if security concerns could be addressed) >>> >> ---------------------------------------------------------------------- >>> >> For information about J forums see http://www.jsoftware.com/forums.htm >>> >> >>> > ---------------------------------------------------------------------- >>> > For information about J forums see http://www.jsoftware.com/forums.htm >>> > >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >>> >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
