Addressing widget not disabled for user input during send
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
People
(Reporter: jorgk-bmo, Assigned: aleca)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
mkmelin
:
review+
|
Details | Diff | Splinter Review |
STR:
Compose a message, add a few recipients
Add some heavy attachments so sending will take some time to complete
Press send.
Observe that the addressing widget is not disabled, so you can change the recipients while sending is in progress. I don't know which effect that will have once sending completes and the sent message is stored.
In any case, this is a regression. The addressing area was always locked from change after the Send button was pressed.
Comment 1•5 years ago
|
||
Note that all other actions in the compose window (except the new recipients area) are using commands, where things like auto-disabling/enabling are very easy to handle in the central command controller, which is observed by all the command consumers. I'm aware that commands logic is part of XUL, but imo it's well thought-out and highly convenient once fully understood, reducing the burden on coders to handle everything directly.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Thanks Jorg for the report.
This is very strange as I remember specifically tackling this aspect when implementing the new addressing widget.
It has been regressed along the way buy other updates, uff.
All right, I'll take care of it right away!
Assignee | ||
Comment 3•5 years ago
|
||
Also, shouldn't be a test covering this scenario?
If not, I will add it because this is quite important.
Assignee | ||
Comment 4•5 years ago
|
||
I found the problem, this is mostly a styling issue.
The input fields get properly disabled but the UI doesn't update to reflect it since the addressing row is a div container and not a real input.
The only real issue is that the msgIdentity menulist doesn't get properly disabled since that's a XUL element and not pure HTML.
A fix is coming.
Assignee | ||
Comment 5•5 years ago
|
||
Comment 6•5 years ago
|
||
Reporter | ||
Comment 7•5 years ago
|
||
On visual inspection, a bunch more elements receive disableonsend="true"
, so yes, they should all be disabled now.
Comment 8•5 years ago
|
||
Assignee | ||
Comment 9•5 years ago
|
||
On it.
Assignee | ||
Comment 10•5 years ago
|
||
Patch updated to disable all the input fields, labels, and pills.
When a pill is disabled all these actions don't trigger:
- pill context menu doesn't show
- unable to select pills via mouse
- unable to select pills via keyboard
- unable to remove rows or pills
- unable to create rows or pills
Comment 11•5 years ago
|
||
Assignee | ||
Comment 12•5 years ago
|
||
The compose tests all pass locally, but I launched try-run just to be sure, even tho we're not changing the behaviour of any section.
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=065d9a6d73d5f550407d873e8cc8cda25d6998ae
Assignee | ||
Updated•5 years ago
|
Comment 13•5 years ago
|
||
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/2075434642ad
Disable addressing widget rows when sending a message. r=mkmelin
Updated•5 years ago
|
Updated•4 years ago
|
Description
•