Search and Top Navigation
#4791 closed bug (notabug)
Opened August 19, 2009 01:14PM UTC
Closed August 26, 2009 02:49AM UTC
Last modified October 11, 2012 09:15PM UTC
widget._trigger inconsistency
Reported by: | Gilles | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | ui.core | Version: | 1.8a1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
There is an inconsistency when you call the _trigger function.
For instance, lets say you have the widget "dummy", inside that widget you call;
this._trigger('somemethod');
This means that element.dummysomemethod is called.
When you bind the function later (e.g.)
var oWidget = $(...).dummy();
oWidget.bind('dummysomemethod', ...);
You can use (from within the widget):
this._trigger('SomeMethod');
but when you bind it with the constructor (e.g.);
var oWidget = $(...).dummy({ somemethod: ... });
You can't use the "SomeMethod" call to trigger it, you have to use "somemethod". In other words, there is a difference in binding and triggering when it comes to casing.
works if you associate
This is as designed.