- animate (UI)
- is this really needed? With the default being false how many people really use this?
- disabled (both)
- max (UI)
- Mobile pulls this from the target element seems needed for backwards compatibility for UI
- min (UI)
- see max
- orientation (UI)
- might be interesting in mobile
- w3c spec doesn’t have anything
- Firefox does orient=“vertical” which feels right
- range (UI)
- true - should be its own widget
- min / max - similar to mobiles highlight option
- step (UI)
- mobile uses the attribute
- value (UI)
- mobile uses the attribute
- values (UI)
- Only used when range is to, should be on the new widget
- defaults (mobile)
- part of mobile widget
- highlight (mobile)
- similar to range: min/max option in UI
- intSelector (mobile)
- deprecated in 1.4.0
- mini (mobile)
- why isn’t this just a class on the top most element?
- theme (mobile)
- part of every widget in mobile
- trackTheme (mobile)
- the theme for the highlight (highlightTheme?)
Only listing ones that are default from the widgetFactory
- value (UI)
- mobile doesn’t need because they target a form element
- values (UI)
- only need for range: true, should be part of different widget
- change (UI)
- mobile doesn’t need because they target a form element
- create (both)
- normal event
- start (both)
- stop (both)
- mobile provides an empty ui object
- slide (UI)
Do we want to embrace the use of a slider sitting on top of a form element? Seems helpful but might need to have standalone ability like we have with the date picker.
Is UI going to start doing themes like mobile are we going to use the classes idea or is there a new plan?
Looks like mobile had a range slider but deprecated it in version 1.4.0? why?