Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Did someone make a mistake editing the docs for ng-disabled #11032

Closed
ab-test opened this issue Feb 11, 2015 · 1 comment
Closed

Did someone make a mistake editing the docs for ng-disabled #11032

ab-test opened this issue Feb 11, 2015 · 1 comment

Comments

@ab-test
Copy link

ab-test commented Feb 11, 2015

Just noticed in large bold letters at the top:

"We shouldn't do this, because it will make the button enabled on Chrome/Firefox but not on IE8 and older IEs:"

Looks like this was added as a passing comment by someone and not part of the doc page.

@ab-test ab-test closed this as completed Feb 11, 2015
@ab-test ab-test reopened this Feb 11, 2015
@Narretz
Copy link
Contributor

Narretz commented Feb 11, 2015

It looks like it was put in to clarify that the following code block is an example of what not to do, but as it is it's very confusing and should definitely be rewritten.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants