7twenty

MX Master
  • Posts

    4,695
  • Joined

  • Last visited

  • Days Won

    79

 Content Type 

Profiles

Forums

Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Release Note6

Posts posted by 7twenty

  1. gexxy replied at 2015-1-8 08:16 back.gif

    Any help? Any contact of developer?

    The problem continues in 2 pc

    I've been playing around and while initially I had some weird things happening (like a freeze), after adding some extra ad rules it seems to have alleviated the problem. So while this might not fix it for you it does seem to have helped on my system. It looks like there's some Javascript that doesn't make Maxthon very happy, and by blocking it things seem to be much better.

    As to why other browsers work, I have no idea - but clearly they're able to deal with whatever it is that is causing the issue better than Maxthon.

    You can try adding the following to AdHunter/ABP and see if it helps out as it did for me. The first line is to (hopefully) stop the issue, the others are to remove extra ads that aren't removed by default.

    For ABP (MX4.4.4.600)*.js$domain=gruppoesperti.it

    gruppoesperti.it##div

    ||shoppydoo.it^For AdHunter (MX4.4.3.4000 & lower)*.js*

    ##div

    ||shoppydoo.it^Not sure if the last line works with AdHunter though.

    By blocking the Javascript it may break something on the webpage (possibly Facebook integration as it's part of the JS that's blocked). Or they just might be extra stuff that doesn't really make a difference.

    As for contacting the developers, there's not much more you can do apart from posting here. The resident Maxthon rep hasn't posted in this thread yet, but probably is aware of it. You can try sending an email to support@maxthon.com, but don't expect a reply back.

    Let us know how you go with the above.

  2. It would be nice if someone with more knowledge of AH and ABP was able to explain the differences in how they work and what exactly it is that makes ABP that much better. I've said before that i'm sure it's just a case of the filters being more up to date with ABP as that is the only thing that ABP does. But then there are things that AH always had issues with (video ads and popups) which ABP is purportedly very good at (although that hasn't been my view so far, even though it works well on FF/Chrome).

  3. s_ta_s replied at 2015-1-5 01:14 back.gif

    Your appeal to the Maxthon developers is useless, IMHO. Much more serious errors are not corrected ...

    I know, and I do but I don't think it should just be swept under the rug. ABP users got what they wanted :p

    Also it's one thing to create a skin for the main chrome, but dialog boxes etc are generally not part of a skin (although can be done with a ui/page.dat mod).

    It's not like this is something that needs to be changed every other release (as we've clearly seen). Fix it once and leave it till whenever.

    What annoys me the most is that it's all quick fixes that any decent coder should be able to do in their sleep!

  4. So this is something that i've brought up a few times before. Consistency in Maxthon's UI is somewhat lacking. There are a number of different dialogs, and each one of them has its own differences. I haven't even included SkyNote, which is still stuck in the MX3 style.

    9u2h6a.png

    1 (orange) / Different sized titles

    2 (red) / Different sized tabs

    3 (red) / Different styled tabs (greyscale flat images & text / coloured images & black text / no icons & black text)

    4 (green) / Different sized buttons (and naming? Done/Close)

    5 (blue) / Buttons/tabs not aligned to any elements (Resource Sniffer is good, Adblock dialog elements are all over the place)

    6 (purple) / Icon on title only on ABP dialog (i'm guessing this was requested by ABP - their logo plastered everywhere possible)

    7 / Windows standard chrome on Resource sniffer, but MX chrome on other dialogs. Why not drop the chrome from Sniffer?

    The ABP dialog might still be a work in progress, but even so the framework is there so I don't see how it's that hard to make it correct from the start.

    It might seem a somewhat petty thing to bring up, but the UI is what every user sees and interacts with every day, it should make sense and not make the user wonder if they've started another program because elements look different (i know i'm pushing the point there, but you see what i'm getting at).

    Can whoever does the UI design please spend a few hours (if that) and at least fix some of the above.

    • Like 3
  5. My question is why are you restricting your monitor to a resolution much less than what it can display? It's been a long time since i've used XP, but i'm pretty sure it was pretty good at detecting the monitors maximum resolution - and yours shows 4 more steps available. If it was purely to show the issue, then i'd like to know how many people still use a resolution of less than 1024x768.

    I've tested MX on a tablet with a res of 1366×768, and it was more than viewable. Unfortunately MX isn't very touch friendly, so it never got much more use.

    Also, if you're going to be making MX window that small then clearly you won't be needing all the toolbars etc, so turn them all off and you get more room.

    Once again, Maxthon is a modern browser designed for today's technology, if you can't or won't or don't have the option to use something else then find a browser that works as you want, but you can't expect everyone else to suffer for those that aren't able to utilise it as it is.

  6. SWFlash0 replied at 2014-12-31 23:44 back.gif

    Want to know my opinion on this?

    1. There shouldn't had been support for CSS in the AdHunter in the ...

    Some good points there.

    1. CSS support in AH was a nice a feature, whether it was intentional or not it was handy.

    2. If you disable then you're back to no adblocker? Surely that's worse than AdHunter?

    3. Yep, much less user friendly now. But maybe that's the point if it's supposed to "just work".

    4. It would have been nice if AH was able to be updated to use the same ABP syntax. I'm guessing that probably wasn't an option, or there wouldn't have been any benefit in it's blocking capability in doing so.

    So far it's only the first release, so hopefully things get better. Although i'm not sure what else Maxthon can do?

  7. Seems like a very heavy site. I've had MX freeze for a few seconds now and then when testing on this site. I think it might be something with adblock as it seems to run better with it disabled.

    ALL this problems don't happen with other browsers Great that you tested, and means that we can focus on what is/isn't happening in Maxthon. But just because it doesn't happen on other browsers doesn't mean that something on your system isn't causing an issue with Maxthon that is causing the site to behave weirdly.

  8. RE: update issues - Something in the update system gets borked at times. Also they don't always put the most recent version up for the auto-downloader to find. Nothing more has been explained about that unfortunately.

    RE: the yahoo mail issue - for now I suppose we'll keep things separate. This doesn't seem related to that issue, and i'd be surprised if a simple UA change would fix this problem.

    Firstly, run through the troubleshooting guide. I'm thinking it's related to extensions (#7) or Adhunter (#5). But i'd recommend starting at updating to the most recent version and work down from there.

  9. This has NOTHING to do with any of the following:

    Browser data - so clearing cache/history etc won't help.

    The address bar favourite/history suggestions options in settings - so enabling/disabling won't help.

    Malware or virus related activity.

    Corrupt HDD or Maxthon settings files. (Not sure how it's though that is even relevant... but i've thrown it in there for completeness sake)

    This was first noted in this post back in November.

    It's related to the data source that Maxthon uses to match address bar entries to common domain names. Whether it's created by Maxthon or provided by a third party is unknown, regardless either they shouldn't be there or users should be given an option to enable/disable questionable sites.

    The only solution at this stage is to follow the directions in the post linked above, which will cause ALL suggestions to be removed.

  10. The easiest way to keep everyone happy is just to offer a few options. Sure it's a little bit of work for the dev's but makes things a lot better for the users. If they already have the code to delete after 5 days, then it's not hard to make that 30 or 60 or whatever. They just need to code a dialogue that lets the user choose the amount of days.

    It seriously makes me wonder what these guys get up to sometimes that simple solutions are never offered. Instead they do something that no one would ever even think of because it's just a stupid option.

  11. visited the Merrill Edge website The site is use some javascript to test for the IE/Chrome/Firefox/Safari version. Other sites with similar banners probably do the same.

    Maxthon is still using Chrome 30 in the UA, as that is the code they use as their base. The site wants at least v31.

    So you have a few options:

    - Use a browser that doesn't cause the flag to be triggered.

    - Change your UserAgent to the a Chrome/IE/Firefox one with the required version.

    - Use a custom Maxthon UserAgent and change the Chrome section to 31 or higher.

    - Add *ose.override.js* to AdHunter to stop the Javascript file from loading and annoying you about something that may or may not have any affect on what happens on the site.

    I think there was some talk of Maxthon updating their core, but who knows when that will happen. When that does happen though the issue will be resolved.

    Basically, there is nothing that can be done till they update the MX core, everything else is just workarounds - all of which work, some are more viable than others.

  12. Works fine for me using the standard UA for the WinPC version and also if changed to the Linux UA as noted above.

    So seems to me they're using another form of detection, which would make more sense.

    On the other hand if the UA change does work for you I can't see any reason why you shouldn't use it. If anything it should make the browser more compatible across sites leading to less issues like this.

  13. Good to see you got things working again.

    Looking at the log, there's nothing that really stands out, but you do seem to have a lot of security focused programs, and at times they can cause you grief when they all battle each other. Not to mention a huge number of processes running which just eat up CPU time.

    On the other hand if everything is working well, maybe just leave it alone.

    If it does come back as requested above, a screenshot would be handy.