Open
Bug 395084
Opened 17 years ago
Updated 2 years ago
Values for <mail-urlfield> not getting reset on header expand/collapse, folder change
Categories
(Thunderbird :: Message Reader UI, defect)
Thunderbird
Message Reader UI
Tracking
(Not tracked)
NEW
Thunderbird 3.0rc1
People
(Reporter: alta88, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier:
1. expanding to full headers, then back to collapsed, does not set the collapsed=true attribute for #expandedcontent-baseBox.
2. switching from a news account folder message to a mail/newsgroup folder message does not clear the #expandedcontent-baseBox > label child's value attribute (website url).
these 'ghosts' lead to incorrect results based on valid assumptions of header state.
Reproducible: Always
Comment 1•16 years ago
|
||
alta88, do you still see this with early release (I would think so, but worth double checking before confirming)
(backup your profile first)
http://www.mozillamessaging.com/en-US/thunderbird/early_releases/
Version: unspecified → 2.0
yes, both of these are still true. but since that new header is so bad, so egregiously terrible, i'm not doing any work in Tb lately..
Comment 3•16 years ago
|
||
given we are expecting (and are pushing) people and extensions to tweak the message pane headers, much desired I would think
not sure which, blocking or wanted
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: wanted-thunderbird3?
Flags: blocking-thunderbird3?
Comment 4•16 years ago
|
||
i suspect this blocks.
Assignee: nobody → dmose
Component: Mail Window Front End → Message Reader UI
Flags: wanted-thunderbird3?
Flags: blocking-thunderbird3?
Flags: blocking-thunderbird3+
OS: Windows XP → All
QA Contact: front-end → message-reader
Hardware: x86 → All
Version: 2.0 → Trunk
Updated•16 years ago
|
Target Milestone: --- → Thunderbird 3.0rc1
Comment 5•15 years ago
|
||
As written, this bug describes problems from the point of view of the DOM. It's not clear what the actual user-facing problem here is, so I don't think this bug is in a state where we can consider it blocking at the moment. Can you elaborate on those and renominate if appropriate? Screenshots seem likely to be helpful here. Thanks!
Flags: blocking-thunderbird3+ → blocking-thunderbird3-
it's not a blocker, imo. nor is it user facing. it's just a proper software design no-longer-valid-value-should-be-cleared 101 thing.
Updated•7 years ago
|
Assignee: dmose → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•