projektilski

Members
  • Posts

    187
  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Profiles

Forums

Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Release Note6

Posts posted by projektilski

  1. 1. The number of hidden tabs is still not properly shown if more than 100
    2. When opening more than 18 tabs from bookmarks, an annoying popup asks for confirmation
    3. Maxthon recreates the desktop shortcut with each upgrade and installation, DO NOT DO THAT. Some people like their desktop icon-free.
    4. New tabs do not allow to open their custom homepage (google for example). It is unacceptable to hear that this will not be implemented/fixed. 
    5. New "window", "incognito" and "session" options inside Maxthon also do not open a custom homepage but a builtin one. 

    These are things that are broken for an extremely long time. 

  2. On 4/11/2024 at 4:48 AM, BugSir009 said:

    Hi projektilski, the development team is redesigning this portion and will optimize it in future version.

    Yeah, it worked fine but was broken many releases ago and still not fixed. Redesign or not, I think this is a simple fix 😉

     

  3. 5 hours ago, BugSir009 said:

    Hi projektilski, could you try with portable version using guest account and see if freezing problem persist?

    I will, but the issue is not only freezing but also disregarding default settings and opening PDF in a tab instead. This behavior could be viewed as a malicious practice.

    EDIT: It does not freeze in the portable version using guest mode, but currently it does not freeze in the installed version either. It freezes periodically.

  4. On 1/8/2024 at 7:25 AM, BugSir009 said:

    Hi projektilski, I have checked with the development team on this and they have confirmed that each beta will be push once it is considered stable. Usually the pushing of each version will occur on either Wednesday or Thursday; after we released a new version on Monday and after some testing from users. In case if a version is found to contain quite a number of bugs then the team will not push through the version till all bugs are fixed.

    Thank you for the information. This is acceptable behavior even though when we check "BETA" checkbox we do agree to receive an "unstable" version. So waiting for the user feedback to push it via auto-update should not be necessary, however, it is better to have a slight delay of a few days and receive the latest beta than not to receive it at all :)

    • Like 1
  5. 8 hours ago, Mhzayer said:

    You are right
    I just meant that it's not a big deal if it's not implemented while there are so many urgent issues that need to be addressed

    like being on the latest chromium core

    still it's a good idea they fix that annoyance 

    Yeah, this feature is not crucial, and there are more important things, but if you implement it, it needs to function like in all other applications. Also, that feature is already there, they just need to ditch the idea that "only some beta will be pushed through auto-update feature" and make it so that all betas are included.
    I have multiple devices and it is a big annoyance to check every day if there is a new beta, download it, and then install it manually on all those devices. A fully working feature of auto-update where "up to date" really means up to date would make my life a lot easier. 

    • Like 1
  6. 14 hours ago, Mhzayer said:

    Just imagine it's written Update to some beta versions 
    and live a happy life

    Why would I imagine such a stupid thing? Who wants such a feature? 
    I want to be "up to date" in the full meaning of what "up to date" means.
    If "update to beta" is not checked then I expect the latest stable release at the time of check, and when "update to beta" is checked it should be the latest beta.
    This is how all other software works and Maxthon should follow that pattern.

    • Like 1
  7. 4 hours ago, BugSir009 said:

    Hi projektilski, kindly go to passkeeper and click on settings then select 'password autosave popup'

     

    image.png

     

    There are plans for optimization pf the tabs for future versions.

     

    You could choose not to have MaxNote shortcut in the installation window.

    image.png

     

    Auto update will only be done when it is pushed from our backend. For example from version 8100 to 8101.

    Thanks for the tip about the Passkeeper popup. Why was it turned off in the first place and why is this option hidden on the Passkeeper webpage?

    Creating the MaxNote shortcut is not the same as creating the Maxthon shortcut. Also, it should remember my previous choice if upgrading. I don't want to remove the Maxthon shortcut every time there is an upgrade. I like my desktop (and taskbar) clean.

    Regarding the auto-update option. It is very misleading (and I could say a lie) to have an option "update to beta" checked and that browser says you are "up to date" even though there is a newer beta to be downloaded manually. 

    Maxthon is the only software that I know of, where the "up to date" with the BETA option checked is not "up to date" to the latest BETA.  There is a clear meaning of what "up to date" means and what Maxthon is doing is not that.




     

    • Like 1
  8. A while ago my Maxthon stopped asking to to save passwords on new sites. It does ask to update (if changed) on a previously saved site. This happens with at least 5-10 latest betas (including 8200).

    In addition to this new behavior, it never asked to save a password on the ESXI web interface - this is true for all versions. 

    The bug, when more than 100 tabs are hidden, not showing the whole number of hidden tabs is still there.

    Installation should remember installation settings from before and should ask if we want both icons (mx and note) on the desktop and taskbar and remember those choices. Next time when I upgrade (and it should know it is an upgrade) it should offer previously selected options. I don't like to delete icons from desktop and taskbar every time I do an upgrade.

    Update to BETA version still does not do what it is supposed to do - update to the LATEST beta.
     

  9. On 2/24/2023 at 2:52 AM, BugSir009 said:

    Hi projektilski, this is still pending further discussion and planning by the development team; no concrete decision as yet.

    Hi, any news regarding Manifest V2? This is still a very important issue. If Maxthon stops supporting Manifest V2 it might lose many users, including myself (and I've been using it for 10 years at least). Ublock Origin which depends on Manifest V2 (Not 3) is a must-have.

     

    • Like 1
  10. 7 hours ago, BugSir009 said:

    Hi projektilski, for future release kindly refer to the following release notes: https://forum.maxthon.com/index.php?/topic/27464-maxthon-release-notes/

    The auto update for beta versions will usually be push when there is a major bug being fixed.

     

    Hi BugSir009,
    When you have a checkbox option named "Update the beta version" it implies an update to the latest beta, not major beta which is not the latest. 
    Those who want the beta version and use this option, want the latest beta, nothing else. You should either remove the option or make it the latest beta. If it's not the latest, we need to manually check forum threads (which also do get changed as we can see) to get the latest beta which makes the built-in option useless.