Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Like @jwegner pointed, <strong>your problem isn't with jQuery but is with browsers support to HTML5</strong>.</p> <p>Resuming, today Google Chrome is the only that understands <code>&lt;input type="number" /&gt;</code>. I mean "the only" because it does on a final version. Both Firefox 4 and Internet Explorer 9 promisses that will understand this attribute, but are on Beta or RC now and can't be considered.</p> <p>Like pointed too, <em>Chrome have a bug</em>: when a parent is being animated, the children arrows on the number field stays hidden. If you focus your input and you use keyboard arrows, you'll see that it yet works as an number field. "Just" the appearance is wrong.</p> <p>It does not happens with <code>toggle()</code> because the parent isn't animated, just turns hidden and visible again. But with <code>toggle("slow")</code> an animation happens, then the described bug too.</p> <p>I posted a workaround here: <a href="http://jsfiddle.net/4fBvL/2/" rel="nofollow">http://jsfiddle.net/4fBvL/2/</a>, wich is based on this: <strong>when sliding out, you can use animations. But to show up again, it must be imediatelly</strong>.</p> <p>Another workaround is to use <code>fadeIn()</code> and <code>fadeOut()</code> instead of <code>slideUp()</code> and <code>slideDown()</code>. By some reason, <em>fades</em> doesn't causes the bug.</p> <p>Anyway, the best option is to avoid <code>type="number"</code> for now. After all, you do not want your page to work only in Chrome, right?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload