© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
(In reply to comment #37)
> (In reply to comment #35)
> > This bug is described as happening as soon as FF is opened.
>
> That isn't explicitly stated by the original poster
It's true Michael didn't qualify it. It would be good of Michael to comment here. His statement "happens to me not every link, but very often" plus Duncan's led me to believe it takes very little to set it off.
> and my interpretation of
> Aleksey Nogin's comment #25 is that he was describing a problem that develops
> over time. You could make a case that both what Aleksey Nogin and I describe is
> a separate problem for another bug report.
skip Aleksey's case until flash is eliminated with flashblock and there is a URL or set of steps. Better anyway to stick to just a couple controlled, well known scenarios. See comment about Duncan below.
> Can you suggest a more appropriate ticket that isn't Flash related?
no but there are plenty you can research. bz search and add condition of summary..."does not contain"...flash - here's one limited to linux http://
> > ...but we don't have any URLs form alexsey to test.
>
> That's the problem. The test case isn't as simple as a single URL. It's
> hundreds of page retrievals. And multiple variables involved (browser version,
> page complexity, extensions). Though sites like:
> https:/
>
> seem to exacerbate the problem. Maybe I'll look into creating a JavaScript test
> case that retrieves unique pages (say going through sequential ISBN numbers at
> Amazon) in a loop, and see if it is repeatable.
Doesn't matter how complex the problem is - it must be reduced, by magic and if that doesn't work by brute force. A test case, even one URL *with a set of numbered steps* is key.
Suggest you and Duncan team up.
Also I would seriously reexamine whether this is tabbed browser issue. I think someone said it happens in non-tabbed situations.