Search and Top Navigation
#11097 closed feature (fixed)
Opened February 12, 2015 04:33PM UTC
Closed June 18, 2015 12:30PM UTC
Spinner: Deprecate _buttonHtml() and _uiSpinnerHtml() extension points
Reported by: | arschmitz | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | 1.12.0 |
Component: | ui.spinner | Version: | 1.11.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
With the new classes option this don't make a lot of sense any more. We should just remove them. One related question brought up by Jörn, was if this should really be an anchor, or should we switch to a button?
Attachments (0)
Change History (3)
Changed February 12, 2015 04:40PM UTC by comment:1
milestone: | none → 1.12.0 |
---|---|
priority: | minor → blocker |
status: | new → open |
summary: | Spinner: remove _buttonHtml and _uiSpinnerHtml extension points → Spinner: Deprecate _buttonHtml() and _uiSpinnerHtml() extension points |
type: | bug → feature |
Changed February 12, 2015 04:50PM UTC by comment:2
We're switching datepicker to buttons. Will probably need the same fiddling with CSS to deal with Firefox, but otherwise I see no reason against that.
Changing the ticket since we always have to go through deprecation first.