Trading UU Broken via/Private Trade Feature

[Sniperwax]

Naq and AT can be traded but any UU entered either doesn't work at all giving this message:

You must ask for SOMETHING in return to call it a trade.
Error condition prevented action.

Or it does go through yet is completely blank in the box that should have the UU. Just shows as 0.

Subject: The trade broker reports trade from *xxxxxxxxx to *xxxxxxxxxx of 0 for 1 Naq is complete.

The trade page looks different too it has drop down menus. This is a stressful situation and to make it through this I can only think to myself WHAT WOULD DUDERANCH DO??

[~Thanatos~]

Here is the log:


Trade Maker Trade Partner Goods Traded In Exchange For Time Status Notes
*xxxxxxxxxxxxx *xxxxxxxxxxxxxx 1 Naquadah Mar 18, 2014, 12:18 am Completed.

i know it isnt the best kind of example.. but the field for goods traded is blank.. there isnt anything in it..

anyways i didnt notice this as part of updates.. but this needs to be looked at.

EDIT***

It looks like the same thing happens when trying big amounts of naq.. I tried brokering 140T, and the same "blank" thing happens...

[Dubby_CompGamerGeek2]

everything looks fine to me, but i didn't test anything.

[teesdale]

yeh looks fine... until you go to broker someone and it doesnt work -.-

enter id and amounts to set broker --V

[spoiler][/spoiler]

then when you click "update trade details" this comes up with the amount boxes empty --V

[spoiler][/spoiler]

then if you click 'confirm trade details' it goes back to the broker main screen with the message
"You must ask for SOMETHING in return to call it a trade.
Error condition prevented action."

[teesdale]

trades with a value of over 1000 of any resource do this.

trades with BOTH values UNDER 1000 naq/uu/turns work perfect though...

[Support]

A far too extreme application of an otherwise good idea, failing because of Chrome's inability to handle HTML properly (as I understood it, it worked without a hitch on FF, Safari and IE).

The Trade Broker is back in business for all, with apologies from the chef for cooking up.

[teesdale]

failing because of Chrome's inability to handle HTML properly (as I understood it, it worked without a hitch on FF, Safari and IE).

Chrome > other browsers