When we click on new ask order there is no listing created :( ?
Can you help please

The same problem, but only for some items. Other items are listed normaly.
I noticed there is always empty fields "Fee level", "Order total" etc, if item wont be placed as lot. Page refresh not help.
It would be nice to get some help =))

It doesn't help. I even didn't notice any change between ctrl+f5 and simple f5. But you right I use chrome.

P.S. previous problem solved itself in a time. But new one item of the same type has the same problem now. As I told before other items works fine. I'm sure its not about script issue.

I have been observing a similar behavior--sometimes I would click the new order button, but the page would do nothing.

It bothered me endlessly for a while. It happened sometimes, but not always; and the cause was not apparent at all.
In my case, I finally nailed it down to something probable: at least it is reproducible, now, for me.

If I punch in a price without the leading zero (the zero that precedes the decimal point, for instance, when typing 0.1 as '.1') the 'new ask/bid order' button won't do anything, and the page will not react visibly in any way, too.

However, if you use 'inspect element' on the new order button, you can see errors showing up in the console--and pressing the new order button generates more errors.

Error generated by trying to use a leading-zero-less decimal as price: http://i.imgur.com/ZXz8BVQ.png
Error generated by trying to use an alphanumerical value as price: http://i.imgur.com/GjbAaWE.png

I suppose that the page was doing nothing, for me, because the code was considering ".1" as not being a number--hence the NaN [https://en.wikipedia.org/wiki/NaN] error.

Joto, I know you said in the previous post that the problem should be fixed, but I just redid the procedure above to generate the screenshots; and the error I described still happens.

Cheers~
Judicious

It is still important to note that ".1" is not a NaN value, but a common American English representation for the number '0.1'.
Therefore, two things:

1) The page is still parsing strings that correctly represent a number as NaN;*

2) In both cases, the page is not trapping the error and alerting the user (or correcting his input by inserting a zero), leaving him in the dark about doing something wrong. Just like the "you don't have that many items to sell" warning, code that detects the issue and warns the user would enhance usability.

*Even though the function receiving the string might be following SI recommendations and expecting to see a leading zero, considering this kind of input (which is unequivocal, and introduces no ambiguity, and is common usage) and prepping the argument by inserting the zero would be a nice application of the Unix design principle of being strict with what you produce, but flexible about what you accept.