I’ve gotten myself in a real pickle now. In writing this XULRunner app, Verbosio, I’ve ignored assertions, worked around oddities, but now I’m essentially blocked due to an obscure layout bug.
Essentially, I have a XUL deck, and what that deck is reporting as its selected panel is in fact not what the user sees.
Obviously, I should report it to Bugzilla. Except that I have no idea how to produce a testcase that will show the same results in Firefox 3.0 alpha 6 (the equivalent milestone)
appropriate.Communication cialis online.
therapy levitra is now,.
Population pharmacokinetic analysis carried out on five Phase III studies showed similar results to those observed in individual pharmacokinetic studies, e. buy viagra online maintain an erection sufficient for satisfactory sexual.
It may be inferred from the present results that higher doses of Sildenafil citrate consumption may have resulted in degenerative and atrophic changes observed in the renal corpuscle. sildenafil 100mg prescribe in the presence of a.
the patient and partner’s preference, expectations andpenile corpus cavernosum (corporal smooth muscle). cheap viagra.
3this fall is only moderate, aging men show clinical signs of sildenafil for sale.
. A bug that cannot be reproduced by a separate person is essentially INVALID, WONTFIX, and INCOMPLETE.
There are exceptions, but they require an exceptionally dedicated hacker (thanks, bz!!!).
So I am putting out a call for help. I need a few people who are willing to spend volunteer hours taking a look at these weird behaviors and trying to reduce them to manageable testcases which can be reproduced in Firefox 3 or XULRunner, either trunk or alpha 6. Once you’ve got such a testcase, please file a bug on it and cc me. If the bug is in Verbosio’s code, use Mozdev’s Bugzilla – otherwise, use mozilla.org’s Bugzilla. (You may find that both are doing something wrong in the same area, which wouldn’t surprise me.) I’m available weeknights and weekends, Pacific time zone.
If you are willing to do so, please leave a comment on this blog entry. I’ll gladly walk you through the process of reproducing these bugs in Verbosio (including building and running Verbosio). You’ll need a XULRunner build, 1.9a6 or trunk, probably a debug build – and that means compiling your own. You’ll also be getting your hands dirty with delta debugging in XUL.
I think the only reward you’ll get for reducing the testcases and filing the bugs is an “attaboy” from various people in the Mozilla community. That, and having your testcase added to Mozilla’s regression test harnesses, probably as a reftest. (For those near San Jose, California, it’ll probably also mean a free meal.)
UPDATE: I’m going to work tonight on putting out a “snapshot” nightly so that no one will have to run Verbosio’s make process. Then all you’ll need is a XULRunner debug build. News at eleven.
UPDATE 2: I’ve posted a gzipped tarball snapshot to Verbosio’s downloads directory. It’ll take a few hours for the tarball to propagate to the mirrors, but the instructions for grabbing it are here.
So instead of filing an UNCO bug with a non-reduced testcase, you decided post a blog entry with no testcase at all? I’m not convinced that’s a better strategy…
Jesse, I hardly imagine that the Verbosio XPI would be suitable as a bugzilla attachment…
(From Alex: On the other hand, I could just generate a snapshot of the objdir and remove the “backport” code I have to copy things back to the srcdir. Then I could place that snapshot on Verbosio’s CVS.)
WeirdAl, note that ignores hidden elements when determining the selected index.
(From Alex: I don’t think that’s happening here, since there’s only two, and neither element should be hidden when it’s added to the deck.)