×

Give a tip

7twenty

MX Master
  • Content Count

    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

Everything posted by 7twenty

  1. http://forum.maxthon.com/index.php?/topic/24527-mx6-questions-and-discussions/#comment-129713
  2. Can someone explain how having blockchain tech in a browser makes it more secure? I (think) I understand how it works in relation to a transaction process, but what/how does it offer security in a browser context?
  3. Yep it does make you cry doesn't it... Seems it's not fixed, the issue is back although doesn't seem to be as repeatable as it used to be. Might have been a one off or something. Given the number of posts of issues of the most recent beta, it seems the core upgrade has caused a lot of issues. Being a user who used to use MX everyday as my only browser, i've now gone to Vivaldi, using MX for various things like logins that i haven't moved over yet. But this bug could well be the one that pushes me right off the edge. It's just too annoying having to close the browser just to make
  4. Not sure what the video will show, but anyways... 7sec Kodi.exe is started using a keyboard combination Video is selected and starts to play on 2nd screen (not shown) 21sec Maxthon.exe restores from being minimised to a window and steals focus NOTHING is pressed or done between 7sec > 21sec If Maxthon.exe isn't running Kodi.exe keeps focus as it should. From the focus detection program shown in the video: 41608:C:\Users\me\Desktop\focus\focus.exe | Mon Dec 17 22:30:14 2018 << FOCUS.exe started 6412:C:\Windows\explorer.exe | Mon Dec 17 22:30:16 2018 5
  5. been having this issue as well of late. Very annoying!
  6. Yes Nothing, it's just another option for those that don't want to use the built-in Maxthon version.
  7. how interesting, and concerning. there's no reason why you can't unpack the extension and have a look at the code, even better if you've got the dodgy chrome version to compare against. As you said, many MX addons were user created/ported rather than official versions from the dev, so depending on how up to date the uploader kept it, it could still be safe. At this stage probably best not to use it if anyone is at all worried about these revelations.
  8. Being unable to comment has been like that for ages. Was answered by a bug* when i questioned it some time ago. Apparently something to do spam i think, so they disabled comments to counter it. As for does it work? Well depends on what you deem "work" means. It does show and allow you to download the available extensions. In that respect, yes it does work. As for a means of being a place for user feedback - it's now useless, and developer information - it has never been any good for that. While that would be something to hope for, i really, really, really don't think that's happen
  9. You wouldn't, nor was it ever implied that you should if you didn't have the problem. Seems you're the only one making more of this than what there is. There was a problem, a new setting change seems to be related to it, reset it and it's all back to normal. While there's some truth to that, i don't think we need to turn this thread into another "they don't listen to us" thread.
  10. i don't know, I just added 1+1 when i found the problem. Turned out it fixed it. Also why i added "or something" in the last sentence.
  11. had the same happen. it's due to the new font sizing feature they added. Go to settings > Advanced, Web page display. For page font size, select Medium (even if it is already), and it should fix itself. Reset to default should fix it as well. Must be some sites reading the setting differently initially or something.
  12. More details would be handy? Which extensions, which scripts?
  13. Updated with some fixes Will hopefully be on the extensions site shortly
  14. URL link? If the site is grey, then unless they have an option to change, or you want to mess around using the stylish extension to play around with the colours, then you're stuck with how it is.
  15. yeah, i've said this many times for a long time. But i'm referring to the backend of how it actually works, that should be the same. But if using the same rules works in one and not the other then there is something else going on.
  16. I thought that they used basically the same ABP core, but it seems that may not be the case. Or at least there's something going on that is causing this issue.
  17. I've never seen that file running, nor is it running now, yet i'm streaming spotify perfectly right now. Sounds like it might be related to the app rather than the webplayer. I'm still thinking it's to do with the way MX is setup to download the extra DRM components, possibly using the mxup.exe program which portable doesn't include. And speaking of which I was just reading this comment again: And i'm thinking, why? Why would they not include the extra 6mb (2.4mb when compressed!) in the download package? If it gets downloaded at first start the data still gets used? It doesn
  18. There's a setting in the skin3.ini file (in UImain.dat) for maxTabWidth = 220,232 Based on it's name i'd say it will do what you want, but can't be certain. Haven't played around with it. And the tab colours can be changed in the constants.css file (or skin_c_dark_const.css if using a dark skin), also in UImain.dat @const TAB_ACTIVE_BG: @const TAB_BG: Set those to whatever colour you want. Again, not tested, but looks to be what you want.
  19. And there it is... So it looks like the installer version auto-downloads the widevine DRM components which allows it to play. For whatever reason the same doesn't happen with portable. Why that is the case i'd be interested to know. Copying over the files downloaded/installed from the installer version allows it to work. I had to refresh the page even after a restart before it worked, but got there in the end. So for anyone with the issue you can: 1 / use the installer version; 2 / install the installer version, copy the files in core\plugins to the same folder in the portab
  20. This is what doesn't make sense to me. I've tried every new version released (all portable, all clean extracts with no userdata) and they all have the same issue. Might be time to try the installer version...and see if that is the difference. Although still doesn't explain what the difference is, or why it's happening.
  21. 10? i don't think so. MX4 is I think. MX5 is only 6 from what i can gather. And think there is an update coming in the coming months, so that should close the gap slightly. Although, while the spotify issue is still occurring, i'm not sure if it's the old blink version that is causing the problem - only for the fact that PHYR is saying that it's working.. Still confused. Although i have to say i've been looking around for another browser, in part because of this issue... not a happy camper!
  22. Wish i could... played around with everything i can think, no dice. This is one of the reasons I wish MX was more of a chrome clone... at least things like this wouldn't happen.
  23. I think there might be some confusion as to what the extension does. To my knowledge there's no option on YT that does what you want. So if the extension can be converted it should work, assuming that it also works with the new YT update. I've had a quick look at it, it's a little beyond what i know as there's a couple of chrome API's that i'm not exactly sure how to to implement in MX. It might entice me to learn something more, so I might spend some time poking around.