Skip to content
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

Define a policy / best practices on when using domStyle / domConstruct / etc. API or the DOM equivalent. #3

Open
pruzand opened this issue Jan 21, 2014 · 1 comment

Comments

@pruzand
Copy link
Member

pruzand commented Jan 21, 2014

We need to define when it makes sense to use the dojo/domStyle/domConstruct/etc API and when we should rely on the DOM/JS API.

for ex: see https://github.com/ibm-dojo/delite/pull/79/files#r9025460

@asudoh
Copy link

asudoh commented Jan 21, 2014

I think, in general, if a thing can easily be achieved by vanilla JS it would be more preferable. Most of the additional features that dojo/dom* API provide seem to be either abstracting different browsers' behavior or fixing nasty issues with DOM. We may want to create the list of such things somewhere, in Google Drive or in this GitHub issue?

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

No branches or pull requests

2 participants