rick.lane

MX Master
  • Content count

    349
  • Joined

  • Last visited

Community Reputation

101 Excellent

1 Follower

About rick.lane

  • Rank
    Assistant Mage

Profile Information

  • Gender Male
  • Location Colorado, USA
  1. Works fine for me in both 5.2.7.1000 and 5.2.7.1100; haven't tried 5.2.7.2000 yet. I'm guessing that these are the versions you are referring to as there isn't any 5.7.2.x versions yet. The new core versions are 5.3.8.x. Edit: Just extracted 5.2.7.2000 portable and 'drag and drop' works as usual for me; used it to get to this thread. Can't speak for the install version; I don't use it anymore.
  2. In regard to the returning to the top of a page, would a mouse gesture that returns the page to the top work for you? That is what I have one set for and it works fine for me.
  3. 5.3.8.300 is a beta version which contains a new upgraded core and is not for regular users daily use as their default browser. 5.2.7.1000 is the current final release with 5.2.7.1100 released recently is a beta upgrade of that series.
  4. 5.3.8.300 gone?

    I brought all of this up when it was first posted but Tony told me it was "not a big deal". So, I just waited to see who else might find it interesting. All I ever wanted was an explanation from someone other than us users. I only brought it up here because since it was originally posted in a thread titled 5.2.8.300 it might be why Kilmitar couldn't find it; that thread it appears has now been edited to be titled 5.3.8.300 and everyone can find it now.
  5. 5.3.8.300 gone?

    Remember that it was first posted under the heading 5.2.8.300.
  6. new beta problems

    I have noticed this as well but didn't relate it to the new beta at first, just thought it was me. Thanks for posting this.
  7. [5.2.3.800] youtube pauses on start

    Just what version are you talking about? There is no version 5.2.3.800, unless you have a very old version; we've been on 5.2.7 for a while now. The latest beta release was advertised as 5.2.8.300 but in actuality the download file is 5.3.8.300 and it shows up in Help> About as 5.3.8.300 (also that is the version number for the maxthon.exe file)
  8. PASSKEEPER DOESNT WORK

    Well, that makes more sense; I don't have it tied to my phone so just my password is all that is required and that is why I have never experienced this problem. Thanks for the response.
  9. PASSKEEPER DOESNT WORK

    Maybe I'm not doing what you are or understanding what you are talking about, but I just accessed Passkeeper from the menu and from the QA page link and was able to login using my longtime password with no problem and have never had any issue with that. ( Not sure what you, No.1, are referring to with regards to "the same code I was sent")
  10. 5.2.8.300

    Is it not a big deal because you didn't discover it? I don't think most of what you complain about are big deals either as I don't experience any of them, such as your complaint that the download file is corrupt, which I have never experienced, but I don't tell you that your concern is "no big deal" It's not that bugsir had a finger problem, it's that the version is miss numbered. Bugsir had it right in that the version should be numbered 5.2.8.300 as that is in line with all of the numbering over the last 15 years. If in fact it is going to a new series of 5.3 versions, then it should be 5.3.1 as this would be the first one in a new series.
  11. 5.2.8.300

    How about the version number discrepancy? Am I the only one that noticed it? Did no one read my post above? All the talk here is about a 5.2.8.300 version (that doesn't exist) when the actual version download file and the resulting Maxthon version is 5.3.8.300. What's up with that? Please acknowledge BugSir006.
  12. 5.2.8.300

    First download of portable worked fine for me, but I find that the actual version number is 5.3.8.300, not 5.2.8.300, both in Help>About and hovering over the maxthon.exe in File Explorer, which made me wonder why a jump from 5.2 to 5.3 as well as jump from .7 to .8. Now it looks like it might be that a mistake was made rather than an intentional version number update from .2 to .3 with the update to .8 being because of the core change. The download files, both install and portable, also indicate 5.3.8.300 though title of the page is 5.2.8.300. I also notice that the default user agent (using What's my user agent at https://www.whatsmyua.info/) has Maxthon as 5.3.8.300. "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 Maxthon/5.3.8.300". Note also that the Chrome version is not up to date (72.0.3626.109 is the latest Chrome on my installation). However I am using the default Maxthon User Agent because I had problems with some sites when I used a custom User Agent with Chrome set to 71.0.3578.98 a few weeks ago.
  13. You don't need to uninstall Maxthon via the Windows app list. If you installed the install version, simply delete the folder you installed it into. And if it was a clean install, which it sounds like it was, also find the data folder in AppData>Roaming>Maxthon5 and delete that as well and just start over. If you are using the portable version, it is even easier; just delete it all and start again. In either case, maybe even download the version again just to make sure.
  14. Skins for MX 5.1.2.3000 [Customizables]

    Thanks for your quick response. Don't know what you did, but re-downloading the file and applying the extracted files solves this issue! Thank you very much.
  15. Skins for MX 5.1.2.3000 [Customizables]

    I'm starting a new post so as not to be lost if I edit a previous post. Wilser, I have found that applying your "Alpha Tab Bar below The Bookmarks Bar" skin to Mx 5.1.0.1400 causes my Maxthon Multisearch to display improperly. It displays the proper results but it is only in the right hand side of the results window and can not be moved via the lower scroll bar or stretched by dragging. Using a single search such as Google or Bing results in a properly displayed search result, filling the whole window. Hope this screenshot helps explain the issue. Not sure why this happens only when I apply your skin. I discovered that the skin affects this because I was testing a newer 5.1 internal release and Multisearch worked fine right after installing. But after I decided it was okay to apply your skin, that's when I discovered this issue was still there. I can post some other screenshots if that helps with your being able to diagnose this issue. Thanks as always for your skin work.