Crash in SetFocus after pasting
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
People
(Reporter: rkraesig, Unassigned)
References
Details
(Keywords: crash)
Attachments
(1 file)
|
526 bytes,
text/html
|
Details |
(Broken out from Gecko crash bug 1793909.)
From bug 1793909 comment 5:
One of our users reported a reproducible crash
https://crash-stats.mozilla.org/report/index/f422d38a-5b74-4080-8eb7-f492a0240710#tab-details
with these STR:
- Go to this website: https://streamable.com/uvlx0k
- Right-click on video and select 'Copy Video URL' option
- Paste into new compose window. Window hangs.
- Click with mouse pointer on 'To', 'Subject', and content sections, app crashes.
We can't reproduce it. Note that the HTML pasted from FIrefox (not Chrome) contains absolutely placed content, xref bug 1276391.
(The user in question is CC'd on this bug as xpilarz0, and has been helpful in trying to pin this down further.)
In bug 1793909 comment 11, it's confirmed that the HTML fragment pasted into the message window is the only relevant bit (i.e., the Firefox metadata isn't causing it). The fragment, which follows below, describes an offscreen position: absolute div.
Version:0.9
StartHTML:00000138
EndHTML:00000324
StartFragment:00000172
EndFragment:00000288
SourceURL:https://streamable.com/uvlx0k
<html><body>
<!--StartFragment--><div style="position: absolute; user-select: text; top: -1000px; left: -1000px;">https://streamable.com/uvlx0k</div><!--EndFragment-->
</body>
</html>
In bug 1793909 comment 18, it's noted that the crash does not occur if any text is entered into the message window before the paste is performed.
To avoid any dependence on streamable.com's current code, an analogous fragment (which has been confirmed to reproduce the crash) can be obtained from the attached "copy-test.html" file.
The underlying crash bug 1793909 does appear to exist in Firefox — crashes with this signature are only mostly Thunderbird.
We have been unable to reproduce the crash on the user's machine in Firefox, however, and I have not been able to reproduce it locally in any application.
|
Reporter | |
Updated•1 year ago
|
|
|
Reporter | |
Comment 1•1 year ago
|
||
And of course as soon as I ask someone else to take a look at it, I figure out what's going on almost immediately.
This is almost certainly a Windows bug — it occurs in Windows code, and all examined reports of this crash have reported OS version 10.0.15063 (Windows 10 version 1703).
Description
•