Hi Peter,

Is this still an issue? The error you describe sounds like a jStore problem but I tested it in IE7 and it works.

Thanks,

Kanwei

On Fri, Dec 17, 2010 at 6:34 AM, Peter peter@maubp.freeserve.co.uk wrote:

Hi all,

I've recently been testing Galaxy on Microsoft Internet Explorer, IE6 and now IE7. It seems that the "peep" view for history entries isn't supported. The history elements' names are not links, so clicking on them does not make them expand to show the info (e.g. number of sequences of file size, and the start of the data).

This happens both on the public Galaxy instance at Penn State (http://usegalaxy.org) and our local Galaxy instance.

Is this a known issue?

Peter _______________________________________________ galaxy-user mailing list galaxy-user@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-user

Weird.. the proxy shouldn't be relevant. Could you open the javascript error console and see what the error is?

On Thu, Jan 27, 2011 at 8:57 AM, Peter peter@maubp.freeserve.co.uk wrote:

On Wed, Jan 26, 2011 at 7:49 PM, Kanwei Li kanwei@gmail.com wrote:

...

Hi Peter,

Is this still an issue? The error you describe sounds like a jStore problem but I tested it in IE7 and it works.

Thanks,

Kanwei

Hi Kanwei,

I just tried the public Galaxy at http://usegalaxy.org aka http://main.g2.bx.psu.edu/ and also ttp://test.g2.bx.psu.edu/ which says it tracks the galaxy-central repo, and for both the history peep links don't work. This is using Internet Explorer version 7.0.5730.13, which I believe is the current release (from back in 2007), from two different Windows XP machines at our institute (which are accessing the internet via a proxy - perhaps relevant?).

Peter

On Thu, Jan 27, 2011 at 6:07 PM, Kanwei Li kanwei@gmail.com wrote:

...

Weird.. the proxy shouldn't be relevant. Could you open the javascript error console and see what the error is?

OK - but how? There is no sign of a javascript error...

I've been to menu Tools / Internet Options... / Advanced tab, then under the "Browsing" category unchecked the box that says "Disable Script Debugging" (to enable debugging), and also checked "Display a notification about every script error". I still don't see any javascript error when using Galaxy.

I've tried following http://www.phpied.com/javascript-console-in-ie/ e.g. putting javascript:debugger; in the URL box will bring up the debugger - but then what?

On Mon, Jan 31, 2011 at 11:14 AM, Leandro Hermida softdev@leandrohermida.com wrote:

Hi everyone,

I posted a similar thread back in August

http://lists.bx.psu.edu/pipermail/galaxy-dev/2010-August/003224.html

There are a couple web UI issues with Galaxy when using IE, like as mentioned in this thread in the history pane data items the link is missing and you cannot expand them to "peep" at what's there.

Glad to know its not just our setup where the peep links don't work on IE7.

Thanks!

Peter

On Mon, Jan 31, 2011 at 5:54 PM, Leandro Hermida softdev@leandrohermida.com wrote:

Hi,

In IE go to Tools -> Internet Options -> Advanced Tab, then under Browsing section:

Uncheck "Disable Script debugging (Internet Explorer) Uncheck "Disable Script debugging (Other) Check Display a notification about every script error

Then you will see the Javascript error when you try to reload the Galaxy page and then try to expand a history item.  I would help debug the Galaxy IE issues but I am at work and cannot change these settings on my work computer (the are grey out :( )

-Leandro

I had done ""Disable Script debugging (Internet Explorer)" and "Display a notification about every script error", but not "Disable Script debugging (Other)". However I still don't see any javascript error when using Galaxy.

Peter

The empty tool pane issue for IE is now fixed on tip as well.

Thanks,

-K

On Fri, Feb 18, 2011 at 3:13 PM, Kanwei Li kanwei@gmail.com wrote:

All:

I retested under IE7 and found the bugs you were mentioning. This has all been fixed on trunk by using a newer local storage library. The only IE7 issue that I am now aware of is when the tool pane is empty when using workflows. Please let me know if you see any other issues.

Thanks,

K

On Mon, Jan 31, 2011 at 1:06 PM, Peter peter@maubp.freeserve.co.ukwrote:

...

On Mon, Jan 31, 2011 at 5:54 PM, Leandro Hermida softdev@leandrohermida.com wrote:

...

Hi,

In IE go to Tools -> Internet Options -> Advanced Tab, then under

Browsing

...

section:

Uncheck "Disable Script debugging (Internet Explorer) Uncheck "Disable Script debugging (Other) Check Display a notification about every script error

Then you will see the Javascript error when you try to reload the Galaxy page and then try to expand a history item. I would help debug the

Galaxy

...

IE issues but I am at work and cannot change these settings on my work computer (the are grey out :( )

-Leandro

I had done ""Disable Script debugging (Internet Explorer)" and "Display a notification about every script error", but not "Disable Script debugging (Other)". However I still don't see any javascript error when using Galaxy.

Peter

---

galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev

On Mon, Feb 21, 2011 at 9:48 AM, Peter peter@maubp.freeserve.co.uk wrote:

...

On Fri, Feb 18, 2011 at 3:13 PM, Kanwei Li kanwei@gmail.com wrote:

...

All: I retested under IE7 and found the bugs you were mentioning. This has all been fixed on trunk by using a newer local storage library. The only IE7 issue that I am now aware of is when the tool pane is empty when using workflows. Please let me know if you see any other issues. Thanks, K

On Fri, Feb 18, 2011 at 10:50 PM, Kanwei Li kanwei@gmail.com wrote:

...

The empty tool pane issue for IE is now fixed on tip as well. Thanks, -K

Hi Kanwei,

I presume this was the fix for the peep view not working on IE7, https://bitbucket.org/galaxy/galaxy-central/changeset/1dfad17e81a8

That doesn't seem to have been included in the latest galaxy-dist release.

I've tried both main.g2.bx.psu.edu and test.g2.bx.psu.edu with IE7 and the peep view is still unchanged. Should the test machine be working? Perhaps there is a caching problem...

Also, when using either main.g2.bx.psu.edu or test.g2.bx.psu.edu with IE7 I am now getting a JavaScript error when I click on any tool:

Line: 52 Error: Object doesn't support this property or method

Offending line:

var section_title = $(this).parents("div.toolSectionWrapper").find("div.toolSectionTitle").text().trim();

Context:

// Log clicks on tools. $("div.toolTitle > a").click( function() {    var tool_title = $(this).attr('id').split("-")[1];    var section_title = $(this).parents("div.toolSectionWrapper").find("div.toolSectionTitle").text().trim();    var search_active = $(this).parents("div.toolTitle").hasClass("search_match");

// Log action.    galaxy_async.log_user_action("tool_menu_click." + tool_title, section_title,    JSON.stringify({"search_active" : search_active})); });

This may be unrelated, but you said you'd been working on the tool pane too, so I'm mentioning it here rather than starting a new thread or filing a bug..

And another JScript error, possibly related, but which I am unable to reproduce reliably:

1. Goto main.g2.bx.psu.edu or test using IE7 2. From the right hand pane, select delete history

(I often find I need to refresh the history pane here otherwise it shows the old deleted history, and also sometimes it still leaves the current dataset shown)

3. Click on Get Data, Upload File 4. Ignore this error (don't debug):

Line: 52 Error: Object doesn't support this property or method

5. Select a FASTA file, click execute 6. Middle pane shows green Job added to queue message 7. Long wait with no feedback other than occasional increase in IE progress bar...

(Again sometimes the history pane has gone back to showing the deleted history)

8. Click on the blue history refresh button 9. Sometimes get error:

Line: 17 Error: 'E.activeEngine()' is null or not an object

Debugging says this is a JScript anonymous function:

(function(aP,E){var ae=aP.document;var a=(function(){var bf=function(bA,bB){return new ... /* * Sizzle CSS Selector Engine * Copyright 2011, The Dojo Foundation * Released under the MIT, BSD, and GPL Licenses. * More information: http://sizzlejs.com/ */ (function(){var bj=...

Hopefully that is enough to reproduce or guess what the problem could be.

Peter

Hi Peter,

The error when clicking tool menu links is now fixed on galaxy-central tip. Thanks for reporting!

On Mon, Feb 21, 2011 at 4:48 AM, Peter peter@maubp.freeserve.co.uk wrote:

...

On Fri, Feb 18, 2011 at 3:13 PM, Kanwei Li kanwei@gmail.com wrote:

...

All: I retested under IE7 and found the bugs you were mentioning. This has

all

...

...

been fixed on trunk by using a newer local storage library. The only IE7 issue that I am now aware of is when the tool pane is empty when using workflows. Please let me know if you see any other issues. Thanks, K

On Fri, Feb 18, 2011 at 10:50 PM, Kanwei Li kanwei@gmail.com wrote:

...

The empty tool pane issue for IE is now fixed on tip as well. Thanks, -K

Hi Kanwei,

I presume this was the fix for the peep view not working on IE7, https://bitbucket.org/galaxy/galaxy-central/changeset/1dfad17e81a8

That doesn't seem to have been included in the latest galaxy-dist release.

I've tried both main.g2.bx.psu.edu and test.g2.bx.psu.edu with IE7 and the peep view is still unchanged. Should the test machine be working? Perhaps there is a caching problem...

Also, when using either main.g2.bx.psu.edu or test.g2.bx.psu.edu with IE7 I am now getting a JavaScript error when I click on any tool:

Line: 52 Error: Object doesn't support this property or method

Offending line:

var section_title =

$(this).parents("div.toolSectionWrapper").find("div.toolSectionTitle").text().trim();

Context:

// Log clicks on tools. $("div.toolTitle > a").click( function() { var tool_title = $(this).attr('id').split("-")[1]; var section_title =

$(this).parents("div.toolSectionWrapper").find("div.toolSectionTitle").text().trim(); var search_active = $(this).parents("div.toolTitle").hasClass("search_match");

// Log action. galaxy_async.log_user_action("tool_menu_click." + tool_title, section_title, JSON.stringify({"search_active" : search_active})); });

This may be unrelated, but you said you'd been working on the tool pane too, so I'm mentioning it here rather than starting a new thread or filing a bug..

Peter