Jump to content

Mr-Yellow

Community Member
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mr-Yellow

  • Rank
    Occasional Contributor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The fix is to use a browser with Flash. I'm going to avoid doing that. Just as the browsers themselves are. I really hope they have a plan for charts when Flash goes away entirely. edit: I assume they have the new CFD interface ready to go and will turn it on at some stage. I'd like to start using it now.
  2. Allowing Java and Flash is not a solution in a world where Flash is deprecated. IG needs to update their charts to the same system running on the CFD end. Reducing my security on a page specially dealing with financial information is nowhere near ideal.
  3. I haven't been able to view charts on IG (share account) for probably a year or more now. When will IG migrate them off the deprecated Adobe Flash interface and onto something which works with modern browsers?
  4. I'd like to edit my post but the time has passed. Too verbose. Keep it simple. Flash, still, ROFL!!
  5. > Make sure Java and Flash are set to 'Allow' Hang-on, I thought this might be the case but couldn't believe it. They're **still** trying to use Flash here? Even though many browsers no longer support it? Share accounts are not upgraded to the same system as CFD charts? This seems to be a blocker bug which should be fixed with priority. Flash charts were dead months ago, no excuse to be still pushing Flash on people.
  6. Thankyou for taking this seriously and fixing the UX failure of trying to track tabs in backend. Now they open in the same window like every other website. Awesome.
  7. > html5 rather than JS lol > auto close any attempts at a second Yes. If the backend state gets out of sync with the actual browser state then this functionality instead closes any new attempts to open a FIRST "platform" window. > you have no idea about. Oh the irony. > To be frank I’m always curious as to why a single individual seems to think that have a better grasp of things over a multi billion pound company with hundreds of devs working on it. Devs need user feedback or issues like this remain undetected. Thanks for your valuable contribution.
  8. > My accuracy on this strategy is over 85%. This is how these "chop shops" work. They are your counter-party so if you start winning too much they cut you off. > If a trader just like me trade and loose money everything would be fine Yup.
  9. > told it’s only me experiencing this so developers won’t look at it You too eh. Seems this is an all too common occurrence. There is nothing about reporting software issues which requires someone else to have already once reported the same issue. If this were the case developers would be entirely blind to the things users report.
  10. I reported this to helpdesk however due to it being a sync issue and having no clear steps to duplicate, and because the individual support person had not received any similar reports I was told it would not be forwarded on and no ticket would be created for developers. So instead I am forced to come here and make a noise. The site has a async/sync issue where if a browser crashes (something the javascript code involved can do often enough) then the backend is left in a state where it breaks the sites UX. * Crashed tab * Click Chrome button to restore it. * "Platform" tab is insta-closed * "Open platform" results in a tab opening which is insta-closed. * No further action can be taken in the system without first logging out and in again. > it was originally developed that the platform could only be open in one tab per browser This is entirely inappropriate for any website. I manage my tabs and windows in my browser, no site should interfere with the normal functioning of a web browser. This is the antithesis of good UX. > Unless it is something that can be replicated we are unable to raise it as an issue. Being a sync issue I would require your full dev environment to build a system which could duplicate such a **bug**. This obviously is not something I can do, so demanding duplication of such a sync issue is not productive in any way and does not lead to any improvement in the IG systems. Please open a ticket so the developers can be made aware of this actual issue in their system. I'm sure they know that this kind of code is always a bad idea but someone in middle-management through they were a genius. Unfortunately said genius is not a UX expert and has messed up your system.
×
×