#8284 closed feature (invalid)

Opened May 01, 2012 10:32AM UTC

Closed May 01, 2013 08:30AM UTC

slidecreate event - ui.value is undefined

Reported by: enumag Owned by: enumag
Priority: minor Milestone: 1.11.0
Component: ui.slider Version: 1.8.20
Keywords: Cc:
Blocked by: Blocking:
Description

http://jsfiddle.net/NPx4z/1/

The initial value is already set by .slider( ... value: 10 }, then why is it not available in slidecreate event handler?

Attachments (0)
Change History (5)

Changed May 01, 2012 12:16PM UTC by scottgonzalez comment:1

_comment0: This is not a bug. Widgets weren't designed to provide any data in create, because everything is already available via the options. However, we have started adding data in cases where it would make reusing event handler easier. In this case, it a stop or change handler could be doubled up on create. → 1337909177700000
type: bug → feature

This is not a bug. Widgets weren't designed to provide any data in create, because everything is already available via the options. However, we have started adding data in cases where it would make reusing event handler easier. In this case, a stop or change handler could be doubled up on create.

Changed October 11, 2012 02:53PM UTC by scottgonzalez comment:2

milestone: 1.9.0 → 1.11.0

Changed October 15, 2012 03:51PM UTC by tj.vantoll comment:3

status: new → open

Verified that this is still an issue in 1.9 - http://jsfiddle.net/tj_vantoll/A6xf4/. It does seem like the value would be useful to have in a create method.

Changed April 16, 2013 08:23PM UTC by scottgonzalez comment:4

owner: → enumag
status: open → pending

Actually, I'd like to know what the use case is, since the value can be queried pretty easily.

Changed May 01, 2013 08:30AM UTC by trac-o-bot comment:5

resolution: → invalid
status: pending → closed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!