![]() ![]() Resolved problems with crashes and freezing when assembling some types of video streams.Now IDM converts audio and mixes with video into one file Resolved the problem when IDM saved video and audio streams as two separate files.Fixed a bug when downloading some types of videos freezing at the end of the download, and fixed other minor bugs.Fixed getting cookies of the downloads that have not been added from browsers automatically.Fixed a problem with randomly disabling IDM extension in a browser.Fixed a bug that caused Windows Explorer to crash.Fixed a critical bug when a new instance of an executable file (for example, from the command line, etc.) closed the process of old instance opened earlier.Fixed mp4 video assembling problems for some streams when audio did not play, or when video played too fast and only the audio played, etc.Resolved problem with download error "400 Bad Request".Also please update "IDM Integration Module" add-on to version 6.41.7 in Firefox to see all downloading options. ![]() ![]() Fixed problems when some web sites had only MKV options and no options of MP4 downloading in Firefox browser.Resolved problems with video recognition on several web sites.Fixed problems with downloading from several sites.Added a correct processing and conversion for some types of MP4 video streams.Improved video recognition for some web sites.Fixed a bug when the download panel was shown even when it was turned off.Fixed problems with downloading for several types of video streams.You may also check for updates manually at any time using "Help→Check for updates." IDM main menu item. Once a new version becomes available, IDM will show a dialog that describes all new features and suggests updating your current version. It now feels more like a corporation making software as a chore rather than making it 'straight out of the heart'.IDM has an automatic update option, and IDM can check for the availability of a new version once per week. While they still seem to care about the open web and Firefox, that passion for making the internet a better place has faded significantly. Some for the better, and many ways for worse. I know this is a long post and that most people in Mozilla are more concerned with Firefox but I started using Firefox at a time (2008) when the organization promoted the other products more often. Will the SeaMonkey council and Thunderbird project separate themselves from Mozilla eventually? I get that Firefox is their flagship product that impacts the most people but I still do not like how Mozilla is treating the SeaMonkey council and the Thunderbird project. It seems that for the past four to six years, Mozilla has been focusing more on Firefox than Thunderbird or SeaMonkey. Will Thunderbird and or SeaMonkey adopt the Photon UI in Firefox? If not, what would the implications be for having inconsistent UIs? Given that Thunderbird supports extensions will Thunderbird adopt the WebExtensions API? I heard that the Thunderbird project is facing similar issues. Personal: Can a SeaMonkey user tell me about how and why the like the suite so I can understand why some people value it? What will happen to SeaMonkey in the near future and it's leadership? How will they rewrite SeaMonkey to bring it up to par with Firefox 57+ given the limited resources or SeaMonkey? Will SeaMonkey adopt electrolysis (mutli-process tab isolation)? SeaMonkey is making some revenue through a sponsorship with DuckDuckGo as the default search engine.īut I am confused on some things and I would appreciate answers to them please.ĭoes SeaMonkey currently support WebExtensions or will so in the future? They would need to migrate off XUL and implement some kind of compatibility with e10s or the suite might not survive for much longer. This can be very problematic for the SeaMonkey community (regardless of how small it is) since the development of the internet suite is dependent on the who writes the code.Īlso, it seems that they have little resources to do a rewrite of SeaMonkey to bring it up to par with Firefox 57+. I noticed that the development team (which consists of less than 12 people) is struggling to keep up with bug fixes and newer features to the Gecko engine. From my understanding, they are autonomous from Mozilla and are mostly on their own in terms of development. It seems that the SeaMonkey council is facing some serious problems with the future and sustainability of the project. ![]()
0 Comments
Leave a Reply. |