Demo page should include examples of input types

[WhatFreshHellIsThis]

trafficstars

So we can test a known good configuration to troubleshoot. For example:

<input type="color"

<input type="datetime-local"

For all of them ideally.

[mreinstein]

I would definitely like to figure out how to make webshim run in jsfiddle. that would be a good step towards building several dozen (maybe hundred) examples and link them to the documentation.

[mreinstein]

@aFarkas would you be able to provide a minimal webshim bootstrap demo in jsfiddle to get this started? I can spend some time expanding various demos for each feature.

[aFarkas]

Do you mean something like this: http://jsfiddle.net/trixta/VNuct/?

[WhatFreshHellIsThis]

I looked at that jsfiddle and it's not what I meant exactly; it's showing the polyfilled controls instead of the native ones in chrome, must be set to hard override or something. What I meant is for those that want to test the polyfill feature it should just have simple html 5 input samples for each type that is polyfilled only as necessary so we can see it in action.

[aFarkas]

Yes the demopage uses:

webshims.setOptions('forms-ext', {
    replaceUI: 'auto'
});

which means, that input widgets are not replaced on smartphone, but on desktop/tablets. I don't really understand your usecase for webshims here. Most people want to see what the webshim work is, if they implement webshims. Additionally, they do use a modern browser to do the first test. So it's most likley, they want to see, how the polyfills look like and not how the native implementation is looking like.

I have added an enhance switch to some of my demos, which showcases the different states of "enhancements". Here is a simple demo for this: http://afarkas.github.io/webshim/demos/demos/mediaelement/track-demo.html

Or here is another example: http://afarkas.github.io/webshim/demos/demos/webforms/datalist-experiment.html

[WhatFreshHellIsThis]

Thank you for that information aFarkas, my use-case is to use webshims to shim older browsers or browsers that do not support certain controls as html5.

The issue is if I'm testing the non-html5 supporting browser and want to see what the shims will do under those circumstances so I can tell if they will be a good fit for my project and also to see if they will work when my own don't in a case of mis-configuration or early development / learning.

I like your switch suggestion, perhaps one big one at the top to turn off auto so we can see only what it will look like when it shims only the necessary bits.