Commit Graph

13 Commits

Author SHA1 Message Date
Moonchild d5a2c45aad Issue #1656 - Part 6: Clean up the build files 2020-09-23 15:52:00 +00:00
Matt A. Tobin 0ddd00f195 Issue #439 - Remove tests from toolkit/ 2020-02-25 15:07:00 -05:00
Matt A. Tobin 0ab5c6474c Issue #65 - Remove AppConstants from toolkit/components/thumbnails 2020-02-06 09:34:25 -05:00
Gaming4JC d0b4eb41bb Issue #756 - Remove contextual identity from BackgroundPageThumbs.jsm
reverts m-c 1279568, 1309699, 1310112
2019-03-18 19:28:33 -04:00
wolfbeast f560671b66 Include blankthumb in the correct file. 2019-02-05 11:00:30 +01:00
JustOff 6bdbb9cdf6 Use a separate process to generate thumbnails only when multi-process mode is enabled 2018-10-27 21:35:56 +03:00
wolfbeast 8c3d0aaca0 Fix a test (#670) 2018-10-19 09:15:54 +02:00
wolfbeast 3555533f7f Convert trinary to more explicit statement. 2018-07-26 23:14:11 +02:00
wolfbeast 9fc1381e11 Fix #include and potentially undefined Capture.options object. 2018-07-26 21:45:34 +02:00
wolfbeast 19b35e9251 Use a fixed thumbnail placeholder for blank thumbs (failed to capture). 2018-07-25 13:45:48 +02:00
wolfbeast e437d80133 Use try/catch in PageThumbs writeData to deal with null data from caller.
Quick fix for #670
2018-07-25 12:34:50 +02:00
wolfbeast de85309fb1 On failure, save a dummy file from the background page thumb capture module.
If a background page thumbnail capture fails (e.g. due to too heavy scripting), we should
write -something- to the thumbnail cache, because otherwise it will try again and again,
which is problematic for bad trap pages, that even if the user has left the page never
to return again, the thumbnail service may still try to capture, and fail.

This resolves the only problem for us in #592.
2018-07-04 23:58:35 +02:00
Matt A. Tobin 5f8de423f1 Add m-esr52 at 52.6.0 2018-02-02 04:16:08 -05:00