Skip to content
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.

datepicker markup too complex #71

Closed
kennywangjin opened this issue Sep 1, 2015 · 4 comments
Closed

datepicker markup too complex #71

kennywangjin opened this issue Sep 1, 2015 · 4 comments
Assignees
Labels

Comments

@kennywangjin
Copy link

to show a datepicker to a user, there are too many lines markup code.
is that possible to generate these markups via javascript, just like jquery ui datepicker do:
// input type='date'
//
//$('input[type="date"]').datepicker({});
//
this seems more convenient to use......

@CuddleBunny
Copy link

+1

@gokunymbus
Copy link
Contributor

We will definitely take a look at that. Thanks for your input.

@wdo3650
Copy link
Contributor

wdo3650 commented Sep 14, 2015

A simplified DatePicker is in the develop branch. See issue #115 . Thanks for your input @kennywangjin.

@wdo3650
Copy link
Contributor

wdo3650 commented Oct 1, 2015

After discussing this component both internally and with the community, we believe it makes more sense to remove the jQuery-generated markup from DatePicker, since Fabric is more focused on the styling of components independent of its JS implementation. This puts the markup straight in the DOM, as it was before, allowing easier access to the elements, attributes and css without the need for Javascript to accomplish everyday tasks.

Thank you for the feedback. It prompted a great discussion internally about about what Fabric should focus on.

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

No branches or pull requests

6 participants