Closed Bug 221013 Opened 22 years ago Closed 22 years ago

Dropdown list of headers is broken in composition window

Categories

(MailNews Core :: Composition, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: fredbezies, Assigned: sspitzer)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-fr; rv:1.6a) Gecko/20031002 Firebird/0.7+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-fr; rv:1.6a) Gecko/20031002 Firebird/0.7+ This is a young regression (less than 24 hours). In order to protect my privacy (and avoid swen worm), I made an invalid adress in to: and insert my real one in Reply-To: But, When I answer to a post, both lines (reply-to: and newsgroups:) are blocked on to: option. I try to switch in headers list, but it didn't work. Reproducible: Always Steps to Reproduce: 1.Built a CVS based trunk Mozilla or Thunderbird (it appears on both) 2.Go to a newsgroup 3.Select a post to reply 4.Try to switch any headers... Actual Results: No switching Expected Results: switching of headers must work
*** Bug 221059 has been marked as a duplicate of this bug. ***
OS: Windows XP → All
This is actually worse than described: You are not only unable to switch the dropdown state but it does not even stay in the state it is given from the chosen action, i.e. replying to a newsgroup message should set the dropdown to 'Newsgroups:' which doesn't work any more. The result is that you are completely unable to reply or compose to newsgroups directly. :-(
Yes, this is surely the nastiest bug I've ever seen since Mozilla 0.8 :) And - what a pity - it breaks both Mozilla MailNews and (my favorite ""toy"") Thunderbird :(
Attachment 132546 [details] to bug 221059 is a screenshot of the situation described in comment 2.
*** Bug 221112 has been marked as a duplicate of this bug. ***
It's quite useless to complain about what's wrong. We need to find what checkin caused the regression. I already tried to check all mailnews patches of the last four days in my two weeks old local code. But none led to this error.
In answer to last comment, bug seems to appear around bugfix for bug 135357 / bug 220913. Why ? Because I build Thunderbird (where I first see the bug) with 9 hours of delay with mozilla.org main time. Also, my last build (for TB and also Mozilla trunk) is "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031001 Thunderbird/0.4a" So regression was introduced in 30th september (afternoon or evening) Hope it helps :)
Oh great, these two are my bugs. But I'm running for a week with them and can't reproduce this. I can only see the problem in the official Linux and Windows builds. Could you back out the patches from 220913 and then 135357 in your local build and test again?
Well, just tell me how to do it :) And I will see :) But the problem is there is no JS console error to help debugging :(
This is a regression from patch to bug 113173. I made a complete checkout of the current CVS and backed out the patches from 20031001 one after another. After removing 113173 the problem was gone. Since there are not few changes in this patch and I don't know the code, I can't say what's wrong in detail. CCing David as it was his patch.
I only see the problem using the header in the first row, not the other rows. (Note that the XUL for this is in addressingWidgetOverlay.xul .)
This may have something to do with the use of a "#" character inside the IDs interacting with my XBL changes. (If XUL had a DTD, using a # inside an attribute of type ID would be invalid: see http://www.w3.org/TR/REC-xml#id .)
When I click on an item in that menupopup, nsXULElement::SetAttribute is _not_ called. For the menupopup that works (second row), it is called for the "selected" attribute, with value "true". It looks like the call should be coming from http://lxr.mozilla.org/seamonkey/source/xpfe/global/resources/content/bindings/menulist.xml#176 or http://lxr.mozilla.org/seamonkey/source/xpfe/global/resources/content/bindings/menulist.xml#314 but I'm not sure (since it's just coming across the XPConnect barrier when it does and I can't figure out how to get Venkman to let me debug that code...
Depends on: 221186
Fixed by checkin for bug 221186. bryner found the problem (I null-checked the wrong variable).
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
*** Bug 221222 has been marked as a duplicate of this bug. ***
Thanks for fixing it :) My new thunderbird is rock solid here :)
*** Bug 221269 has been marked as a duplicate of this bug. ***
*** Bug 221511 has been marked as a duplicate of this bug. ***
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.