pantantrollo

Members
  • Content count

    529
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Everything posted by pantantrollo

  1. VERGONZOSO, we continue with the same problem of access to web with digital certificate (with blink engine, with IE yes it works) v.5.2.2.1000. Other browsers with blink engine, work OK
  2. Updated User Agent

    How do you know or verify that google uses that string you mention? Will you refire to look for a page that the user-agent tells you and check it from that same search instead of going directly to the page? I do not know, in my case, whether searching from google or loading the page directly, I get the same (v.5.1.7.2000) (if that is what you were referring to) Mozilla / 5.0 (Windows NT 10.0, WOW64) AppleWebKit / 537.36 (KHTML, like Gecko) Chrome / 55.0.2883.75 Safari / 537.36 Maxthon / 5.1.7.2000 In your case, the correct one is the second, I think maxthon 5.2.xxx carries the core 61
  3. Updated User Agent

    Precisely in the series 5.2, has updated the core from old core 55, so imagine how is the matter :-)
  4. Totally agree. Personally every this is looking grotesque. If this same error had occurred in any other renowned browser, already would have fallen sticks in some digital media. If you look at the changelogs of the series v.4.9 and the beginning of the series v.5, there is a difference in the list of errors that have been corrected, brutal compared to what has been going on for a few months. Or resources have been diverted to things like cryptocurrencies and other things, or the thing looks worse and is being left to die
  5. V.5.2.1.6000 portable, same errors
  6. They are different topics. It does not have to do with the SSL / TLS connections, but with the request of the window that gives access to our digital certificate (the one that has it, of course) Of all, you will see that it works in other browsers, including maxthon v5.1, and it does not work in maxthon 5.2
  7. You will not have a valid certificate. In my case, they work perfectly, Cent-browser, chromiun, Opera, and above all, maxthon 5.1 chromiun : Cent-browser, Opera maxthon 5.1 I have stopped trying because I think there are enough proofs
  8. to @No.1MaxthonFan and @Magdalene , Have you tried to log in with a digital certificate "from" those pages? . I know that the pages work, the error comes after trying to log in The problem is that the window to choose the digital certificate is not displayed. The configurations are exactly the same for v.5.1 as for v.5.2. In v.5.1, YES, jump the certificate choice screen. (The change of UA, has no effect). The links to login This is the window that has to come out and does not come out in v5.2,
  9. V5.2.1.5000, Errors on the web that request digital certificate follow. https://www.sede.fnmt.gob.es/certificados/persona-fisica/verificar-estado (capture above) https://sede.sepe.gob.es/GesUsuariosSEDE/GestionUsuariosTrabajaWeb/intro_seguridad.do https://empleocastillayleon.jcyl.es/oficinavirtual/comprobarPIN.do?srvc=mostrarLeerDni&tpdstn=2 And basically I got tired of trying the ones I usually use V.5.1.7.2000 works correctly in all of them
  10. Unsolved Series v 5.2.x, error in the access to certified stores with the ultra core (series 5.1 yes they work) more
  11. Arowana skin 5.2.5.600

    +1 :-)
  12. I think that this should also be @@||maxthon.cn^$document
  13. There are a few threads/comments recent about it EDIT: Look to see if it works, I just edit it, there was an error
  14. ABP needs an upgrade

    What version of "Noads" do you have to work with v5.1.5.1000? I answer myself , seen in another post: http://forum.maxthon.com/index.php?/topic/22883-noads/
  15. extensiones

    Ningun problema por aqui, entro bien. Un Saludo.