I can confirm this bug is reproducible and still present in TB 93.0b5 (64-bit) on Windows 10 Pro (64bits). This is quite problematic because the 'File' | 'Save As' | 'File' | HTML Files is quite often used to create .html signature. If you compose a new email add an image with web absolute path (eg: https://www.mydomain.com/img/image.png), when saving into .html file, only the file name (image.png) appears in the src attribute of the img tag... preventing the image to be loaded from its absolute path. This was perfectly possible in TB till recently possibly broken since 78 but not sure exact version. Also if you had a working signature and you suddenly need to update it, then the image is lost because the absolute path that was already present in existing signature is non longer preserved upon saving :-( Which is a bug from end-user point of view! The reproducible method used to insert image and save signature is as follow: - Create a **New Message** - **Insert > Images...** - Set **Image Location** as *https://www.mydomain.com/img/image.png* <-- change it to a valid path for your test :-) - Set** Alternative Text** as *Company Logo* - **Ok** - **File > Save As > Files...** - Set **Filename** as *signature.html* - Set **Save As Type** as *HTML Files* **Result**: Upon saving the *src* attribute is set to *image.png* instead of *https://www.mydomain.com/img/image.png* in the *signature.html* file **Workaround**: Edit the .html file in text editor (e.g Notepad) and correct the *src* path manually then save the file which should not be required. @Thomas, I put you in copy for info as it may affect organisation (and other users) that use HTML signature with linked image (e.g logo) hosted centrally on a web server.
Bug 1676825 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I can confirm this bug is reproducible and still present in TB 93.0b5 (64-bit) on Windows 10 Pro (64bits). This is quite problematic because the 'File' | 'Save As' | 'File' | HTML Files is quite often used to create .html signature. If you compose a new email add an image with web absolute path (eg: https://www.mydomain.com/img/image.png), when saving into .html file, only the file name (image.png) appears in the src attribute of the img tag... preventing the image to be loaded from its absolute path. This was perfectly possible in TB till recently possibly broken since 78 but not sure exact version. Also if you had a working signature and you suddenly need to update it, then the image is lost because the absolute path that was already present in existing signature is non longer preserved upon saving :-( Which is a bug from end-user point of view! The reproducible method used to insert image and save signature is as follow: - Create a **New Message** - **Insert > Images...** - Set **Image Location** as *https://www.mydomain.com/img/image.png* <-- change it to a valid path for your test :-) - Set** Alternative Text** as *Company Logo* - **Ok** - **File > Save As > Files...** - Set **Filename** as *signature.html* - Set **Save As Type** as *HTML Files* **Result**: Upon saving the *src* attribute is set to *image.png* instead of *https://www.mydomain.com/img/image.png* in the *signature.html* file **Workaround**: Edit the .html file in text editor (e.g Notepad) and correct the *src* path manually then save the file which should not be required. @Thomas, I put you in copy for info as it may affect organisation (and other users) that use HTML signature with linked image (e.g logo) hosted centrally on a web server. It would be great if a fix could be implemented and backported to 91.x ESR branch...
I can confirm this bug is reproducible and still present in TB 93.0b5 (64-bit) on Windows 10 Pro (64bits). This is quite problematic because the 'File' | 'Save As' | 'File' | HTML Files is quite often used to create .html signature. If you compose a new email insert an image with web absolute path (eg: https://www.mydomain.com/img/image.png), when saving into .html file, only the file name (image.png) appears in the src attribute of the img tag... preventing the image to be loaded from its absolute path. This was perfectly possible in TB till recently possibly broken since 78 but not sure exact version. Also if you had a working signature and you suddenly need to update it, then the image is lost because the absolute path that was already present in existing signature is non longer preserved upon saving :-( Which is a bug from end-user point of view! The reproducible method used to insert image and save signature is as follow: - Create a **New Message** - **Insert > Images...** - Set **Image Location** as *https://www.mydomain.com/img/image.png* <-- change it to a valid path for your test :-) - Set** Alternative Text** as *Company Logo* - **Ok** - **File > Save As > Files...** - Set **Filename** as *signature.html* - Set **Save As Type** as *HTML Files* **Result**: Upon saving the *src* attribute is set to *image.png* instead of *https://www.mydomain.com/img/image.png* in the *signature.html* file **Workaround**: Edit the .html file in text editor (e.g Notepad) and correct the *src* path manually then save the file which should not be required. @Thomas, I put you in copy for info as it may affect organisation (and other users) that use HTML signature with linked image (e.g logo) hosted centrally on a web server. It would be great if a fix could be implemented and backported to 91.x ESR branch...
I can confirm this bug is reproducible and still present in TB 93.0b5 (64-bit) on Windows 10 Pro (64bits). This is quite problematic because the 'File' | 'Save As' | 'File' | HTML Files is quite often used to create .html signature. If you compose a new email insert an image with web absolute path (eg: https://www.mydomain.com/img/image.png), when saving into .html file, only the file name (image.png) appears in the src attribute of the img tag... preventing the image to be loaded from its absolute path. This was perfectly possible in TB till recently possibly broken since 78 but not sure exact version. Also if you had a working signature and you suddenly need to update it, then the image is lost because the absolute path that was already present in existing signature is non longer preserved upon saving :-( Which is a bug from end-user point of view! The reproducible method used to insert image and save signature is as follow: - Create a **New Message** - **Insert > Images...** - Set **Image Location** as *https://www.mydomain.com/img/image.png* <-- change it to a valid path for your test :-) - Set **Alternative Text** as *Company Logo* - **Ok** - **File > Save As > Files...** - Set **Filename** as *signature.html* - Set **Save As Type** as *HTML Files* **Result**: Upon saving the *src* attribute is set to *image.png* instead of *https://www.mydomain.com/img/image.png* in the *signature.html* file **Workaround**: Edit the .html file in text editor (e.g Notepad) and correct the *src* path manually then save the file which should not be required. @Thomas, I put you in copy for info as it may affect organisation (and other users) that use HTML signature with linked image (e.g logo) hosted centrally on a web server. It would be great if a fix could be implemented and backported to 91.x ESR branch...