Alexander Farkas
Alexander Farkas
Hi, actually this is already integrated into webshim. Currently, I only haven't added the right feature tests to load it, if it's not supported. Currently this is the test: `Math.imul...
@inf3rno I think you overcomplicate things here. rICs are not micro tasks and rIC callbacks are not called at any place in a frame like for example `setTimeout` (tasks) or...
``` webshim.setOptions({ 'debug': true, 'forms': { replaceValidationUI: true, lazyCustomMessages: true, iVal: { fieldWrapper: '.form_fields__field', errorWrapperClass: 'form_fields__field--has_warning', errorBoxClass: 'form_fields__field_warning' }, addValidators: true }, 'forms-ext': { replaceUI: {number: 'auto'}, types: 'number' }...
Please also note, that webshim is actually deprecated.
Sorry, for taking so long. Reason for this is that I'm using the native stepUp and stepDown methods. And it seems that Chrome has changed here something. Will look into...
yeah but I mean the `stepUp` method: ``` js document.querySelector('input[type="number"]').stepUp(1); ```
If you pre-define `webshims.formcfg.en`/`webshims.formcfg['en-US']` and `webshims.formcfg['en-GB']` and include this in your JS, than this will be used instead of the included version.
Another example: Create a file with this content: ``` js webshims.validityMessages['en-CUSTOM'] = { "typeMismatch": { "defaultMessage": "Please enter a valid value.", "email": "Please enter an email address.", "url": "Please enter...
You can try this: ``` css .ws-range, input[type="range"] { width: 0.61538em; height: 199px; } ``` But this CSS should be in sync with this js config: ``` js webshim.setOptions('forms-ext', {...
No, but the idea of the inline margin-left/margin-top is that it always tries to center the thumg inside the range. In case you don't want to center it, you can/should...