Vice Admin
  • Content count

  • Joined

  • Last visited

 Content Type 



Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Everything posted by 7twenty

  1. It's not. The new one doesn't have the left sidebar or the media controls on the right. ABP was the first thing I checked, probably should have noted that above. Old player worked fine with the default and my custom UA. But as above the UA doesn't affect the new site. Originally, i thought I found the solution using Retro.. .but that's no the case. Ads make it not workable. So definitely a bug.
  2. I read something it might be related to the DRM plugin they use. So if MX can't or won't work with it for whatever reason then that's a problem. Although the weird sync issue thing is well... weird.
  3. Skins for MX [Customizables]

    hmmm interesting. Still unsure what they're for?
  4. Skins for MX [Customizables]

    Can I ask a stupid question? What are the files in the start folder for? They don't open with the MXpacker and I can't figure out what their for or how they're created?
  5. Don't run script on mxaddon:// page

    Tried that as well, but still doesn't work. Doing my head in... and it's possibly one tiny character that i missed.
  6. How do i stop an extension that runs at "doc_start" from running on it's own options page? Have tried the "exclude" setting in the def.json file, but no matter how it's written it won't stop it from running. Have even tried adding code to check the URL and if it's the GUID for the extension to stop running the script... but somehow it still continues? Makes no sense to me. PS if I get a reply to this i'll be completely surprised!
  7. Dark and light theme icons

    The built in tools icons (downloader/sniffer etc) change colour depending on theme colour. He's asking if the same can be done for extension icons. I think you probably could but you'd need to find out how to detect the status of the theme (dark/light). Not sure where about that is saved. And i'm not sure what you would use as a trigger. If the check is only done on click then the icon will stay till you click the button or page refresh etc. On top of that I think that the icon change feature might be broken in MX5. Was testing an extension with code that I know worked (and tested with MX4.9), but the same extension doesn't work in MX5.
  8. Night Mode (MX4 style)

    Ummm it's wednesday and no update on the extension site? @BugSir006
  9. Night Mode (MX4 style)

    Been through a few revisions the past week and a bug fix thanks to a user that posted on the extension site. Now includes a first run prompt to check/save the colour settings, and some minor UI tweaks.
  10. Why are maxthon extensions not compressed?

    Just noticed this when I was playing around with packing a skin file. It seems the old version of the MXpacker file does actually compress the extensions/skins files. On the test that I did using the skins and an addon it shrunk the file by approx 40-50%. IIRC your extension is one of the larger ones, so if you want to compress it then use the old version. Apart from that and it's command line based (although you can drag n drop) i'm not sure what else thee is different. But the files created still work. Attached below as i'm unsure if it's still available anywhere else. MXpacker_old.zip
  11. Extensions Can't be Loaded

    Check that syncing extensions hasn't accidentally been turned off in the sync settings.
  12. DraftKings Login issue

    Confirmed. you get an "enter a username" error if it's entered by using Passkeeper or entering directly.
  13. How to add MX4 Skins to MX5 V5.03.900 beta

    Doubt it would work, or might cause some issues seeing as there's quite a few differences in the default UI in MX5. Unless the skin was a complete UI update, I think it will have some problems displaying. Haven't tested though. This. Seems they've added support to allow using .mxskin files... now if only there was someone to create a skin...
  14. Decided to double check the fixes... and yes the ones marked in the image are fixed, yet the ones noted just below that (as quoted above again) are still not fixed. Does everything need to be an image and marked with the issues for things to change? Should it have been bolded? Bigger? Pink? *sparkles* and fireworks maybe? There's a saying in English - Do it once and do it right. I guess there isn't a similar one in Chinese?!? Give me access to the files and i'll do it directly instead of waiting 2.5 months for the job to not be done properly...
  15. [Script] Clear the Cookies of the current site

    Confirmed here as well.
  16. CTRL+B or Menu > View > Favourites bar
  17. Night Mode (MX4 style)

    Updated on the extensions site. Hopefully will be available on Monday ;-)
  18. Night Mode (MX4 style)

    just an update with this. Working on adding a settings page to adjust the colours. Code's a bit of a mess but does the job. But that's what happens when you learn as you go. Will hopefully have the updated version up within the next few days. Still haven't got around to seeing if it can be enabled on all pages. Might be next on the to do list.
  19. Probably not going to get a reply... but will give it a go and see what happens. I'm having trouble getting the "activate" parameter of the newtab function to work when the string is called from a variable. In: mxTabs.newTab({url:"url", activate:true, position:"afterCurrrent"}); when activate is set to true or false directly in that line it works fine. If I have a variable "openTab" set to true or false and called in that same line "activate:openTab" it also works. But if I have a variable "openTab" with a value set to true or false which is determined from some javascript, and then saved and called via the mx.storage api, it never seems to work and always defaults to "true". Doing an alert (openTab) or rt.storage.getConfig("openTab") shows that the string is correct. Getting quite annoying, as I know what I want to do and i'm pretty sure i've got it all right, but this just won't work.
  20. Official translator on Crowdin

    Ummm, you already are:
  21. Update? Also, on the Passkeeper lock screen there is a space after "welcome". This is due to a non-standard character being used as noted above. There is no translation string found for this on Crowdin. Fix it and add it to Crowdin.
  22. Export passwords

    Seems that might not even be possible. Chrome and Opera at least only show Firefox and IE when trying to import data.
  23. Export passwords

    I don't think Maxthon supports exporting passwords. If you're moving to another browser hopefully it can import them directly.
  24. Can't download tutorials

    This is what Google has for developers: https://developer.chrome.com/extensions This is what Microsoft has for developers: https://docs.microsoft.com/en-us/microsoft-edge/extensions/api-support/supported-apis This is what Mozilla has for developers: https://developer.mozilla.org/en-US/Add-ons This is what Opera has for developers: https://dev.opera.com/extensions/ All the information related to extensions (and other stuff) is on their developer pages. Maxthon on the other hand, requires you to go to the extension/skins sites (not an issue), but then the links Maxthon Extension SDK / Beginner Tutorials / Submission and Update Process / Approval Criteria, all lead you to the MX forum... then you have to download a compressed version of a MS word file to access the info. We're in 2017, and this is a web browser company yet still making people do things in such a convoluted way like we're still in the 90's. No one is asking that it's as complex or in depth as the sites above. Just bring the info to the web where it should be. All the info in the forum posts mentioned above should be on this "MX developer site", and any competent coder should be able to convert those .doc files into a website relatively easily. That plus direct download links to the examples and the MXpacker. This is just one example of the "many are issues that could be updated fairly easily" but not done, mentioned by MaxthonGuy. This would take someone less than a few days to come up a perfectly workable site, and would rarely be needed to be updated (given how often that info has been in the past). And even when it does it's just a matter of updating those sections that's required, the same way the .doc file would have been updated anyway.