Bugzilla

(In reply to ISHIKAWA, Chiaki from comment #12)
> (In reply to ISHIKAWA, Chiaki from comment #11)
> > Bug 1682772
> > comm/mail/test/browser/composition/browser_attachment.js is failing due to similar reason discussed here.
> > I am saying this because I see the same dialog that gets stuck in this and the other test.
> > 
> > Oh, already known in comment 1.
> 
> Wait. I thought I was seeing exactly the same dialog in this and the other test that got stuck. But comment 5 and/or comment 6 suggests otherwise?
> 
> TB seems to ask for the file to SAVE and that is where it stopped proceeding. 
> You can see that in https://bugzilla.mozilla.org/show_bug.cgi?id=1682772#c15, I attached the screen dump of the stuck dialog which even has a file name in the input line of the file chooser.
> So something is not doing it right from there.

With the fix, the test in bug 1682772
> > comm/mail/test/browser/composition/browser_attachment.js 
no longer gets stuck but returns with an error. A progress.
More in bug 1682772.

(In reply to ISHIKAWA, Chiaki from comment #12)
> (In reply to ISHIKAWA, Chiaki from comment #11)
> > Bug 1682772
> > comm/mail/test/browser/composition/browser_attachment.js is failing due to similar reason discussed here.
> > I am saying this because I see the same dialog that gets stuck in this and the other test.
> > 
> > Oh, already known in comment 1.
> 
> Wait. I thought I was seeing exactly the same dialog in this and the other test that got stuck. But comment 5 and/or comment 6 suggests otherwise?
> 
> TB seems to ask for the file to SAVE and that is where it stopped proceeding. 
> You can see that in https://bugzilla.mozilla.org/show_bug.cgi?id=1682772#c15, I attached the screen dump of the stuck dialog which even has a file name in the input line of the file chooser.
> So something is not doing it right from there.

With the fix, the test in bug 1682772
> > comm/mail/test/browser/composition/browser_attachment.js 
no longer gets stuck but runs successfully. (My early post about a bug was a premature post. It seems if I change browser.ini, I have to re-run 
|make configure| to propagate the proper change of browser.ini? Anyway,  more in bug 1682772.