You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
Empty alt attributes in markdown images in the editor are replaced with undefined or null. ![](/path/to/img.jpg) becomes ![undefined](/path/to/img/jpg)
- If the current behavior is a bug, please provide the steps to reproduce.
For images added in rich text mode:
Add an image block to the markdown editor. Select an image, leave the alt field blank, and save.
Check the updated file and find [undefined] in the resulting markdown. If you're using the cms-demo site (and can't check for a changed file), you can see the result by switching to markdown mode.
For images added in markdown mode:
In markdown mode in the editor, add a markdown image tag with empty []
If you save without ever switching to rich text mode, it will stay, but if you switch to rich text mode for any reason, even on later edits, you fill find the tag now has [null] for the alt.
- What is the expected behavior?
To clarify, it's invalid html to have no alt attribute at all, but blankalt attributes (i.e. alt="") are actually the recommended practice for decorative images. Screen readers will skip images with empty alt attributes, but they'll read 'undefined' aloud, and that's not helping anyone.
- Please mention your CMS, node.js, and operating system version.
Reproduced in CMS 0.7.2, as well as preview/branch deploys of the new UI. Tested on Windows 10 and Mac OS. Tested in Chrome only so far.
The text was updated successfully, but these errors were encountered:
- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
Empty alt attributes in markdown images in the editor are replaced with
undefined
ornull
.![](/path/to/img.jpg)
becomes![undefined](/path/to/img/jpg)
- If the current behavior is a bug, please provide the steps to reproduce.
For images added in rich text mode:
[undefined]
in the resulting markdown. If you're using the cms-demo site (and can't check for a changed file), you can see the result by switching to markdown mode.For images added in markdown mode:
[]
[null]
for the alt.- What is the expected behavior?
To clarify, it's invalid html to have no
alt
attribute at all, but blankalt
attributes (i.e.alt=""
) are actually the recommended practice for decorative images. Screen readers will skip images with emptyalt
attributes, but they'll read 'undefined' aloud, and that's not helping anyone.- Please mention your CMS, node.js, and operating system version.
Reproduced in CMS 0.7.2, as well as preview/branch deploys of the new UI. Tested on Windows 10 and Mac OS. Tested in Chrome only so far.
The text was updated successfully, but these errors were encountered: