I agree with you Siketa. I hate seeing ads saying upgrade to the best Browser on the Internet, and it says Internet Explore 9. I say to myself you can do one and ignore
One annoying bug during installation of 17.x is if you dont set Dragon as defualt browser it will set defualt browser to Internet Explorer, since my defualt browser is Firefox this can be quite annoying at times, I hope comodo can look into this and fix this >:(
Apart from that annoyance I love dragon, I use it as my second browser and often flash firmware on my router with it, is excallant browser, hopefully comodo will keep up great work ;D
I would like to add this comment, because quite frankly I’m not going to take the time to read all of the other posts here. I think it’s freaking annoying as hades, to have this dragon make you update their download it seems every dam* time it seems I get on the net. That is truly a pain in anyone’s rump! Cut the ■■■■ Comodo! Or I’m so very close to ditching your browser, and going back to Chrome or Firefox, just to get away from the ridiculous annoying notices. Sound irritated? You bet I and I’m sure other’s are too!
As I tell the players in the gaming server that I am an Admin of, “We can’t please everyone. We please someone but hurt another in the process, some things we have to just accept.” Also, I would like to quote what we tell players that have complaints about playing in our server, “You are free to play and free to leave, we aren’t forcing you to stay.”
I think a cool feature that could he added that I’ve never seen in any program is say you get an alert that there’s an update but you heard there is a bug with this new version that you don’t like so you click something that says don’t notify again until the next update is available. so say you have dragon 17 and you get an alert to update to 17.1 but you don’t want it so you click don’t notify until the next update is available. so you won’t get another alert until say 17.2 is available or possibly 18 depending on how far the version number jumps. but you won’t get an alert until there is a version available that is newer than 17.1 . also if you you have silent update on but don’t want to turn it off but want to prevent getting 17.1 and dragon hasn’t already installed it you could add an option to skip next update. also if you have silent update off and you get an update alert, add a link to the release notes and known issues. so people can easily make an informed decision
Since the updates were fixed in a small amount of time, do not hold me to what “small” means. An idea of a few hours or a full day will be great. I say that your idea is not bad, holding off for a full version update.
They have not updated since 12 Beta, and we still receive updates. They just keep Betas in the background until they deem Stable and skip Beta phase altogether, regarding the public.
The Chrome team is excited to announce the release of Chrome 17 to the Stable Channel for Windows, Mac, Linux and Chrome Frame. 17.0.963.46 contains a number of new features including:
New Extensions APIs
Updated Omnibox Prerendering
Download Scanning Protection
Many other small changes
Security fixes and rewards:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix
[73478] Low CVE-2011-3953: Avoid clipboard monitoring after paste event. Credit to Daniel Cheng of the Chromium development community.
[92550] Low CVE-2011-3954: Crash with excessive database usage. Credit to Collin Payne.
[93106] High CVE-2011-3955: Crash aborting an IndexDB transaction. Credit to David Grogan of the Chromium development community.
[103630] Low CVE-2011-3956: Incorrect handling of sandboxed origins inside extensions. Credit to Devdatta Akhawe, UC Berkeley.
[$1000] [104056] High CVE-2011-3957: Use-after-free in PDF garbage collection. Credit to Aki Helin of OUSPG.
[$2000] [105459] High CVE-2011-3958: Bad casts with column spans. Credit to miaubiz.
[$1000] [106441] High CVE-2011-3959: Buffer overflow in locale handling. Credit to Aki Helin of OUSPG.
[$500] [108416] Medium CVE-2011-3960: Out-of-bounds read in audio decoding. Credit to Aki Helin of OUSPG.
[$1000] [108871] Critical CVE-2011-3961: Race condition after crash of utility process. Credit to Shawn Goertzen.
[$500] [108901] Medium CVE-2011-3962: Out-of-bounds read in path clipping. Credit to Aki Helin of OUSPG.
[109094] Medium CVE-2011-3963: Out-of-bounds read in PDF fax image handling. Credit to Atte Kettunen of OUSPG.
[109245] Low CVE-2011-3964: URL bar confusion after drag + drop. Credit to Code Audit Labs of VulnHunt.com.
[109664] Low CVE-2011-3965: Crash in signature check. Credit to Sławomir Błażek.
[$1000] [109716] High CVE-2011-3966: Use-after-free in stylesheet error handling. Credit to Aki Helin of OUSPG.
[109717] Low CVE-2011-3967: Crash with unusual certificate. Credit to Ben Carrillo.
[$1000] [109743] High CVE-2011-3968: Use-after-free in CSS handling. Credit to Arthur Gerkis.
[$1000] [110112] High CVE-2011-3969: Use-after-free in SVG layout. Credit to Arthur Gerkis.
[$500] [110277] Medium CVE-2011-3970: Out-of-bounds read in libxslt. Credit to Aki Helin of OUSPG.
[$1000] [110374] High CVE-2011-3971: Use-after-free with mousemove events. Credit to Arthur Gerkis.
[110559] Medium CVE-2011-3972: Out-of-bounds read in shader translator. Credit to Google Chrome Security Team (Inferno).
The bugs [105459], [106441], [108416], [108901], [109716], [109743], [110112], [110277], [110374] and [110559] were detected using AddressSanitizer.
In addition, we would like to thank miaubiz, Drew Yao and Braden Thomas of Apple, Sławomir Błażek, Aki Helin of OUSPG, Chamal de Silva and Atte Kettunen of OUSPG for working with us in the development cycle and preventing bugs from ever reaching the stable channel. Various rewards were issued, including a top $3133.70 reward to Aki Helin.
More detailed updates are available on the Chrome Blog. Full details about what changes are in this release are available in the SVN revision log. Interested in hopping on the stable channel? Find out how. If you find a new issue, please let us know by filing a bug.