Bug identified through BackWPUp installation

[mollywozhere]

WordPress version: 4.9.8
BackWPup version: 3.6.3
PHP version: 7.1.23  (64bit)
MySQL version: 5.6.40-84.0-log
cURL version: 7.59.0
cURL SSL version: OpenSSL/1.0.2k
WP-Cron url: https://www.mollywozhere.com/wp-cron.php
Server self connect: Response Test O.K.
Document root: /home/mollywoz/public_html
Temp folder: Temp folder /home/mollywoz/public_html/wp-content/uploads/backwpup-5b4013-temp/ doesn't exist.
Log folder: Log folder /home/mollywoz/public_html/wp-content/uploads/backwpup-5b4013-logs/ does not exist.
Server: Apache
Operating System: Linux
PHP SAPI: cgi-fcgi
Current PHP user: mollywoz
Maximum execution time: 120 seconds
BackWPup maximum script execution time: 30 seconds
Alternative WP Cron: Off
Disabled WP Cron: Off
CHMOD Dir: 0755
Server Time: 1:3
Blog Time: 01:03
Blog Timezone: Europe/London
Blog Time offset: 0 hours
Blog language: en-GB
MySQL Client encoding: utf8mb4
PHP Memory limit: 768M
WP memory limit: 128M
WP maximum memory limit: 768M
Memory in use: 14.00 MB
Loaded PHP Extensions:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dba, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, json, ldap, libxml, mbstring, mcrypt, memcached, mysqli, mysqlnd, openssl, pcntl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, pspell, readline, session, shmop, soap, sockets, sqlite3, standard, sysvmsg, sysvsem, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

[dd32]

Hi @mollywozhere,

This Trac is for WordPress core development only, and is not a support avenue for either WordPress or plugins.

I expect that debug output would need to be sent to the plugin developers, along with a description of what problem you've encountered is.

I'm marking this as invalid, as no WordPress bugs are included with the report.
If you have identified a bug in WordPress, please feel free to re-open this with details of it, and how to duplicate it without the use of plugins.

[desrosj]

In 44816:

Widgets: Remove change event when editing a Custom HTML widget.

The change event was previously required to ensure that the Customizer picked detected changes to the widget’s content and synced them to the preview. In the current state, though, the trigger( ‘change’ ) is no longer required and is causing issues with the widget’s “Done” and “Save” buttons.

Fixes #45335.
Props audrasjb, afercia, westonruter.

[desrosj]

The above changeset is not associated with this ticket. There is a typo in the Fixes line, and is instead fixing #46335.