On 08/13/10 11:57, Michael Schwendt wrote:
On Fri, 13 Aug 2010 11:48:09 +0200, Joachim wrote:
> On 08/13/10 11:32, Michael Schwendt wrote:
>> On Fri, 13 Aug 2010 11:14:44 +0200, Joachim wrote:
>>
>>> Hi,
>>>
>>> I don't know whether somebody tried the following:
>>>
>>> I wanted to change the component in some bugzilla bug by using firefox,
>>> so I opened the bug on the bugzilla page and pressed the edit button in
>>> the component line (at the top of the bugzilla window) to modify the
>>> concerned component. But immediately after having pressed the edit
>>> button, firefox begins to loop.
>>>
>>> Somebody has seen this?
>>
>> Dunno what you mean with "begins to loop". Clicking the
"edit" link
>> triggers reloading the list of components from the server prior to
>> displaying a combobox.
>
> I have a 2 proc box, and if I press this button, the top command shows
> that 1 proc is fully running with firefox (or opera). I did this in F13
> and F14 alpha, with the same results. Maybe a JAVA issue?
No. Java isn't used.
It works fine here with F13, btw.
Have you tried yet whether emptying your Firefox cache helps?
I was a bit impatient: I had to wait for more than 1 min, until the
component pulldown menu appeared. I think this is too long (even on my
2x1.86 Ghz intel box).
Kind regards
--
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
http://www.rhrk.uni-kl.de/~backes