We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Note: This idea pressupose a few things:
A) plugin must also knows which element are void (, ) B) the syntax MUST NOT be used for non-void elements.
THE IDEA: Tags should be closed when the editor inserts the / character.
EXPLANATION OF THE IDAD:
Thus, the author can always type /, without thinking about whether the element is going to folloow syntax or syntax.
By contrast, today, for void elements, one must type />.
DRAWBACKS: Are there any drawbacks to this idea? Well, you need to make it works even if one types <foo src="/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Note: This idea pressupose a few things:
A) plugin must also knows which element are void (
, )
B) the syntax MUST NOT be used for non-void elements.
THE IDEA: Tags should be closed when the editor inserts the / character.
EXPLANATION OF THE IDAD:
Thus, the author can always type /, without thinking about whether the element is going to folloow syntax or syntax.
By contrast, today, for void elements, one must type />.
DRAWBACKS: Are there any drawbacks to this idea? Well, you need to make
it works even if one types <foo src="/
The text was updated successfully, but these errors were encountered: