Commit graph

14 commits

Author SHA1 Message Date
Ghislain Seguin
c6e49f7b07 Discovered r.js' pragmas use them instead of the hacky solution provided by amd-stripper.js 2012-01-13 17:24:49 +07:00
Ghislain Seguin
dbedf643d3 Specified dependencies 2012-01-13 17:20:43 +07:00
Ghislain Seguin
3f1543a451 AMDized 2012-01-13 17:20:23 +07:00
John Bender
c716ab707a take closestParentPage off of $.fn 2011-12-09 14:39:57 -08:00
John Bender
978762dc67 centralized method for finding closest page data 2011-12-09 12:17:20 -08:00
Ethan Romba
a8c04855b4 Issue #3081: Range inputs on dialogs don't degrade
The degradeInputs plugin bails early for pages that do not have
data-role="page". This behavior prevented range inputs (for slider widgets)
from degrading properly when used in dialogs.

Updated degradeInputs unit tests to check dialogs, too.
2011-11-21 16:47:14 -06:00
Eddie Monge
5535e24c46 Update to add license to root, update individual files to not have license, add license to built and testing files 2011-11-08 15:43:36 -08:00
John Bender
a69e906cc7 add bail if the degrade Input page data isn't present 2011-10-14 15:33:50 -07:00
Gabriele Rabbiosi
9903376f35 degradeInputs now uses the recently introduced keepNativeSelector() 2011-10-14 00:50:29 +02:00
Gabriele Rabbiosi
1559478aae Issue #2654 - 'degradeInputs' plugin doesn't trigger on 'create' events; modified plugin and added tests 2011-10-13 22:21:47 +02:00
scottjehl
b2d023732a Fixes #2490 where IE (and WP7) were not properly degrading form inputs via the degradeinputs plugin (and search inputs were not being styled as such) 2011-09-23 19:17:22 -04:00
scottjehl
bf593857f6 degraded type should have been "text" instead of true. Addresses a comment in issue #2123 2011-08-18 22:01:58 -04:00
Scott Jehl
705ed4f308 typo in comment 2011-07-26 17:04:36 -03:00
scottjehl
79d3aa6f04 brought back degradeInputs page option, this time as a decoupled page plugin file. Fixes #2123 2011-07-26 13:49:10 -04:00