On Fri, Aug 13, 2010 at 12:57:48PM +0200, Joachim Backes wrote:
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).
This is a known issue, because the component list is very long and
(IIRC) is loaded with a JS. I don't know whether the BZ 3.6 update
coming this weekend will help with this issue.
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
Where open source multiplies:
http://opensource.com