Skip to content
This repository

degradeInputs in latest git version gone #2123

Closed
negue opened this Issue July 21, 2011 · 3 comments

4 participants

negue Scott Jehl Andreas Hörnicke Owen Brotherwood
negue
negue commented July 21, 2011

Is this now a new feature or just a bug?

I really would need the feature back .... :)

Scott Jehl

Worked on it today. Almost done. Hang tight :)

Andreas Hörnicke
anho commented July 25, 2011

Need this one too.

Scott Jehl scottjehl closed this in 79d3aa6 July 26, 2011
Owen Brotherwood

By the way, the doc @ http://jquerymobile.com/test/docs/forms/plugin-eventsmethods.html indicates that the type="search" will be degraded to type="text": but the type get's degraded to type="true".
This is an old feature, not caused by the commit.

The code problem could be the:
search: true, // should be search: "text" ???
optType = o.degradeInputs[ type ] || "text"; // the value for search is "true"
if ( o.degradeInputs[ type ] ) { //

And one could save a micro micro sec by having the declaratiom of optType statement in the code segment:
if ( o.degradeInputs[ type ] ) {
optType=o.degradeInputs[type];

Degraded Form Input Types
jQuery Mobile degrades several HTML5 input types back to type=text, or type=number after adding enhanced controls. For example, inputs with a type of range are enhanced with a custom slider control, and their type is set to number to offer a usable form input alongside that slider. Inputs with a type of search are degraded back to type=text after we add our own themable search input styling.

Timmy Willison timmywil referenced this issue from a commit July 26, 2011
brought back degradeInputs page option, this time as a decoupled page…
… plugin file. Fixes #2123
fe98cf8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.