Share this post

Link to post

Share on other sites

Why after every update Maxthon remove languages in Locales folder and put only languages that are in the installation? Now i need after every update to copy my (Bulgarian) language file. The installation must replace existing languages if they have an update and keep other files. Please, correct this!

Share this post

Link to post

Share on other sites

It might not be for creating a skin. But to implement a means to change and load it with the browser running might be closer to rocket science. That said, they had it working perfectly for MX3... so it does beg the question what changed that they had to drop support, and why is it taking so long to bring it back.

- On Youtube website, sometimes I see the download button on the floatbar, and sometimes just the "popup" alone. And when the download button exists, it never really offers to download the video of it.

- On Youtube website, when I choose to make the video float, clicking on the video doesn't respond like on the website (to pause, for example). If it's a general behavior for all websites (which is cool too), please provide a nicer UI for it. At least show the bottom bar upon clicking...

Share this post

Link to post

Share on other sites

- On Youtube website, sometimes I see the download button on the floatbar, and sometimes just the "popup" alone. And when the download button exists, it never really offers to download the video of it.

Links to videos that this happens on would be handy. HTML5 or Flash?

The download issue has been complained about by me for quite some time. They need to get their sniffer to work correctly with the (not) new (anymore) streaming videos.

Share this post

Link to post

Share on other sites

- On Youtube website, sometimes I see the download button on the floatbar, and sometimes just the "popup" alone. And when the download button exists, it never really offers to download the video of it.

make sure you always enable resource sniffer in setting-addon-utility?

Share this post

Link to post

Share on other sites

even if you are not "pushing" and update and no pop-ups are displayed, when someone goes to About, the browser checks for a new version and if there is a new one, like in this case 5.0.2.2000, it shouldn't say "Your browser is up to date". Even if there is no link to the update, it should at least say that there is a newer version available (and it would be very easy to give the version number).

Since 5.0.2.2000 is supposed to be a "final release", I don't think the "beta" issue applies here. I don't see a "check for beta versions" check box in the settings.

Please note that this problem is not something new, so it is obviously something you designed this way on purpose or continue to ignore. Please give us some more info on the topic.

Share this post

Link to post

Share on other sites

even if you are not "pushing" and update and no pop-ups are displayed, when someone goes to About, the browser checks for a new version and if there is a new one, like in this case 5.0.2.2000, it shouldn't say "Your browser is up to date". Even if there is no link to the update, it should at least say that there is a newer version available (and it would be very easy to give the version number).

Since 5.0.2.2000 is supposed to be a "final release", I don't think the "beta" issue applies here. I don't see a "check for beta versions" check box in the settings.

Please note that this problem is not something new, so it is obviously something you designed this way on purpose or continue to ignore. Please give us some more info on the topic.

It was indeed designed this way so that even final versions can be tested before being released to the public. That is not to say your suggestions don't have merit. I'd like to see options to install both untested finals and beta versions. Nice compromise in my opinion.

Share this post

Link to post

Share on other sites

An option to enroll as a "tester" should unlock the possibility to upgrade to either non-public final or beta, then.

However I don't see the point of marking a version as final, if it still needs testing. This, of course, is a topic for software development, but if you need it this way, then make every version introducing new features an "alpha" as a testing version, a bug-check version a "beta" (corresponding to the untested final now) and a stable version for public release will then be the final. It would be somewhat like the Debian releases, but I believe that not introducing new features in the beta would be of great benefit for stability.