From: Jacob Helwig <jacob.helwig@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Frank Li <lznuaa@gmail.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Gerrit Code Review 2.0.3
Date: Tue, 17 Feb 2009 08:13:34 -0800 [thread overview]
Message-ID: <8c9a060902170813ie8f5bc1gfed53e4f31f64c23@mail.gmail.com> (raw)
In-Reply-To: <20090217151838.GI18525@spearce.org>
On Tue, Feb 17, 2009 at 07:18, Shawn O. Pearce <spearce@spearce.org> wrote:
> Gerrit is known to not work in Internet Explorer. As an open source
> developer, my primary desktop system runs Linux. My portable laptops
> all run Mac OS X, because its shiny. I have no system capable of
> running Internet Explorer, nor do I desire to send dollars towards
> Redmond in order to obtain an OS license in order to do so.
>
> Something is busted in the IE AJAX code used by Gerrit Code Review.
> I'm guessing that instead of making the data available to the AJAX
> callback, IE wants to save it as a file on disk. No clue why.
> And due to the lack of IE, I am unable to debug the problem myself.
> I am waiting for someone who really cares about using IE to debug
> it and contribute the patch back.
>
I've found IEs4Linux helpful for debugging IE-only issues under Linux.
http://www.tatanka.com.br/ies4linux/page/Main_Page
I don't recall, off hand, if it'll provide IE 7 (and the site isn't
working for me right now, so I can't confirm this). It does provide
IE 5.0, 5.5, and 6.0, however.
-Jacob
next prev parent reply other threads:[~2009-02-17 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 1:12 [ANNOUNCE] Gerrit Code Review 2.0.3 Shawn O. Pearce
2009-02-17 7:11 ` Frank Li
2009-02-17 15:18 ` Shawn O. Pearce
2009-02-17 16:13 ` Jacob Helwig [this message]
2009-02-17 16:44 ` Johannes Schindelin
2009-02-17 17:09 ` Shawn O. Pearce
2009-02-17 21:06 ` Jacob Helwig
2009-02-18 0:13 ` thestar
2009-02-17 18:53 ` Boyd Lynn Gerber
2009-02-17 9:01 ` Gerrit Pape
2009-02-17 15:13 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c9a060902170813ie8f5bc1gfed53e4f31f64c23@mail.gmail.com \
--to=jacob.helwig@gmail.com \
--cc=git@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).