Support standard attributes in TABLES Policy#326
Open
subbudvk wants to merge 2 commits into
Open
Conversation
Contributor
Author
Member
|
I am sorry, @mikesamuel is the release master. He'll get on this as soon as he can. Forgive the delay! |
|
Hello. What is the current thinking on this? Is "colspan","rowspan" generally safe to allow? |
aalmiray
force-pushed
the
main
branch
6 times, most recently
from
9bb458a to
f40152f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #195 and allows more attributes than existing PR
The goal is to allow common safe attributes in table context for in a single PR instead of handling one attribute at a time. Pl let me know if we want to allow more, or if there are issues with this one.