On Mon, Jan 31, 2011 at 12:44 PM, Peter <peter@maubp.freeserve.co.uk> wrote:

> 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