-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
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
Fix execCommand link #245
Fix execCommand link #245
Conversation
Well, this it's complicated... it's a maintained document, but there is zero expectation of ever standardizing, right? |
@marcoscaceres It's already in that directory, only the link is broken. |
Hey @gked - I suspect you accidentally moved the execCommand document into the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should probably go back into archived. We can still maintain it when there is glaring inconsistencies/errors, but let's not give false hope that it's going anywhere.
What might be useful is to figure out what we might be able to salvage and maybe push that into HTML? This may just be tiny little things, but every little thing we salvage is a win. There would have to be clear evidence of interoperability. |
We decided on the call on Friday to do as you say and put it back into Archived. It does not prevent us from editing the file when need be. |
Sounds great @johanneswilm. Thanks for the update! |
"Archived" also gives false information that those will never be maintained. It should really be "Inactive" or something. (And possibly also renaming |
This is fixed by #264. |
Since it's in ActiveDocuments directory.
Fixes #247