Global Moderator
  • Content count

  • Joined

  • Last visited

Community Reputation

513 Excellent

About Tony

Profile Information

  • Gender Not Telling
  • Location - God's Own Country
  • Interests Platting fog

Recent Profile Visitors

13,181 profile views
  1. and with respect thats part of the problem - users here have long memories of the history of bugs and requests - the bugsirs are ever changing and it seems users requests and/or comments are conveniently forgotten when people move on at Maxthon - that [surely] should not happen - you must have more than a word of mouth system for bugs that can be referred to
  2. i cannot be bothered to search back - 2 months? - if you said 2 years that this bug has been around you would be nearer the mark
  3. i quote No1 above - this bug has been known about for years - certainly the life of MX5 - it has been reported on a regular basis with little or no comment from the ever changing bugsirs - it has been confirmed in the past by the bugsirs and you now confirm it again we are only discussing this bug - if you want a list of other bugs - spelling mistakes - UI errors that have been reported over time that have been given NO PRIORITY what so ever then search the board i and many others can also give examples of features that have been requested that have been ignored just as those same people can give examples of 'features' that the devs have added that no one wants or uses so no issue is important other than the ones the devs think are - as a question - what crash and freeze issues - the board is not alive with reports of this
  4. confirmed - what you really mean is that you have confirmed the bug that was a confirmation of the same bug that has been around since Adam was a lad this just goes to show that the devs ignore all bug reports until someone shouts enough or they fix the bug by chance bug reporting is joke - always has been
  5. Maxthon do surveys or have in the past and then ignore the input - they ask for input for new features or old features to be added back and ignore that as well they know best what we the user wants or think they do - again its how it works - if thats not for you then move on - nothing will change - it never does in a dictatorship icons where you want them is another matter - many [most] things are possible with the UI but thats up to you to work out how to change the UI with a skin - or look for one that has what you want - unfortunately there are few skins these days as most who did them have moved on
  6. an update on the time scale would be useful - this year - next year or when Maxthon10 is released
  7. or even things that no one asks for but the devs crystal ball tells them its sure to be wanted or the other waste of time changing something that works to a bug filled feature
  8. its not the big 1809 - that has now been pulled as far as i know but i got the big one on the day it was released that was build 17763.1 - the update i got today has raised the build number to 17763.55
  9. just got an update for 1809 from Microsoft and the font rendering issue looks to be solved
  10. where the hell are the testers or more to the point do they actually test anything - this was just the latest release that was posted here with no early release in the tester area
  11. translate selected text does not work - boxes are empty
  12. mx5.2.5.1000 - font rendering is still a problem on some sites with Directwrite enabled but i believe this is a Windows 10 [1809] problem that Maxthon and other programs are seeing - i get the same problem on an email client with some received emails whether Microsoft see it that way is another question
  13. tried in 1809 rd5 and the latest insider build and it screws a few sites - same sites tested on edge are fine
  14. if its anything like many of the bugs and requests for additions and changes it will still be a work in progress its only 4 years - dont rush them!
  15. another one to add to the list that wont get fixed