The recent update has fixed the problem for me as well. Thank you to the
developers for working to get that fixed.
Again, I stress that these types of problems are a HUGE deal. I really would
have liked to see some better communication to the community as to how this
problem was going to be handled. If nothing else, as was said by another
member there should have been a downgrade to abrowser 38 as a temporary
option. Is there a policy in place for dealing with this type of thing?
Anyway, thank you for fixing this!!!!
