@rjee198 @Richard.W Nice catch!
2 Likes
I’m comparing the new advanced to the old app. The most obvious lacking feature is that In old app one could reorder tabs by using pressing a tab with mouse pointer and dragging. In new advanced app they seem to be locked in place.
1 Like
Hi @Richard.W, drag & drop reordering will appear very soon along with even more drag & drop functions.
5 Likes
Can some of that drag and drop functionality include re-ordering the items in the detail section? e.g. might prefer to have the instrument details box near the top rather than company details
And I guess other drag and drop will include resizing of the columns in the positions window? The default for the “Instrument” column is too wide for those who use only tickers, and the “quantity” column is wide enough for a number like 10,000,000. (I do not trade penny stocks. 
)
4 Likes
Yes, indeed! 
2 Likes
If I ask or mention where is the… Trailing Percentage Stop Loss will that appear on Monday 
Thanks for the advanced, what are the chances that I asked where that was and 13 hours later pop.
Moved —>
1 Like
Hello, is there any way you can bring this back in the new web app?
3 Likes
@palesths Those features will be added as well.
3 Likes
Great to hear! Really miss this in the new view
any update on the pie into pie feature?
3 Likes
The new app is completely broken in the latest version of Firefox. I get a message telling me welcome to the new app and a button that says continue. On pressing the button nothing happens and I cannot access my account! @George
How odd. I have FIrefox 86.0.1 and the app works perfectly.
yeah, works for me too. probably needs a restart to clear the cache
I have tried multiple times, restarted and cleared the cache. I had to use Edge to dismiss the 'We have a new app" message, since clicking the button on Firefox did nothing. On returning to Firefox the message has gone, but I just get the constant loading icon on all tabs. Clicking on any buttons also does not work.
I have just tried Firefox in safe mode and nothing changed either. I am using ‘Standard’ privacy mode.
It’s very frustrating. Some errors below: @Richard.W
GET https://live.trading212.com/favicon.ico - not found
GET https://live.trading212.com/rest/v1/brexit/consents?countryCode=GB - bad request
Failed to get service worker registration(s): Storage access is restricted in this context due to user settings or private browsing mode. [bundle.js:64:809171]
DOMException: The operation is insecure. [bundle.js:64:809171]
Cookie “JSESSIONID” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite live.trading212.com
Cookie “TRADING_LANG” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite live.trading212.com
Cookie “amp_cookie_testye4-NjmSjpAigabTWk85WO” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 bundle.js:21:99045
Cookie “_tldtest_a2izslrky5-lj-2N1mys6F” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 bundle.js:21:99045
Cookie “_tldtest_bExLZFw6DrsSIx464aT_vg” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 bundle.js:21:99045
Cookie “_ga” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:30:486
Cookie “_gid” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:30:486
Cookie “_fbp” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 783550965065701:21:5381
Cookie “_fbp” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 783550965065701:21:5381
Cookie “_fbp” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
Hi @whitenoise
We are looking into it.
Hi @Y.M thanks for letting me know.
1 Like
@whitenoise I will send you a DM.