Since the most recent Chrome update, attaching files in BT Mail (email.bt.com) no longer works for me. The attachment appears in the compose window with a size and a random filename, but the message can't be sent with it and the compose area stops responding.
Things I have already tried, none of which made any difference:
- Cleared cache, cookies and all site data for bt.com
- Reset site permissions and allowed everything for email.bt.com
- Tested in an Incognito window with extensions disabled
- Rebooted the PC
The same account works fine in Edge on the same machine, so it isn't the account or the network. Chrome is on version [xxx], Edge is on version [xxx].
Opening the Chrome developer console while attaching shows the actual failure. A request to /mail/bin?r=resource... on email.bt.com comes back with HTTP 500 (Internal Server Error), followed by a JavaScript error Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'name') in ux.js. There is also a No such locale en_us message from the same script.
A 500 is a server side error, so this looks like the BT Mail web app failing to handle something the newer Chrome now sends, rather than a problem on my PC. It worked right up until the browser updated, and as Edge is built on the same engine I expect it will break the same way once it picks up the same update.
Is anyone else seeing this, and can BT confirm whether it has been raised with the webmail team? Happy to provide the full network capture from the developer tools if it helps.
