Talk:Comparison of web browsers/Archive 3

order
I have edited the discussion page in order to restore the initial order. In order to preserve this order, please use three equal signs (===) to create sub-sections rather than sections. And please add your post at the bottom of a section. Possible topics are Standards support issues, Features you want mentioned or Browsers you want added/removed. Grey (talk) 03:43, 7 January 2008 (UTC)

System Requirements
Hi All. Thanks for the amazing page. I know it would be hard, but easier than some of the other tables - a table of system requirements, hard disk, OP, RAM size especially would easily allow a reader to determine if he could download and run it. In some cases it's hard to find this data, for example I've just been looking at the Opera site and I can't find any of this information. Considering how much RAM Firefox has been known to use in the past (horribly large amounts) and that not everyone has a new computer, this information would be extremely helpful. Just my two cents worth. Thank you. Blucat David. —Preceding unsigned comment added by 198.142.19.27 (talk) 20:05, 29 July 2009 (UTC)

Call for academic reviews of the web browsers....
--124.78.210.114 (talk) 13:20, 11 February 2010 (UTC)
 * http://scholar.google.com/scholar?as_q=internet+explorer+google+chrome&num=10&btnG=Search+Scholar&as_epq=&as_oq=&as_eq=&as_occt=title&as_sauthors=&as_publication=&as_ylo=&as_yhi=&as_sdt=1.&as_sdtp=on&as_sdts=5&hl=en


 * http://scholar.google.com/scholar?hl=en&q=internet+explorer+google+chrome&btnG=Search&as_sdt=2000&as_ylo=&as_vis=0 —Preceding unsigned comment added by 124.78.210.114 (talk) 13:29, 11 February 2010 (UTC)

The references cited do not seem to be from academic journals very much--124.78.210.114 (talk) 13:32, 11 February 2010 (UTC)

ahahaha,Google? is wiki sponsored by them?

Table notes converted into group references
I notice that the refun had recently been converted into ref which caused the numbers of references and table notes to overlap. Since I figured that might be a tad confusing and refun is up for deletion I converted the tables to use the group list feature of references. This means that table notes should automatically be linked up properly. Hopefully this will make it easier to keep the table foot notes in sync. I left most of the bodies of the notes defined below the tables except for a few cases where nested references forced me to move them to avoid citation warnings. The rest could be moved up if desired, I just wanted my change to be easily diff-able. If you have any questions about how this works, see Help:Footnotes or Footnotes or ask. Note the occasional use of syntax to handle the special cases of normal references nested inside grouped references. PaleAqua (talk) 10:29, 10 March 2010 (UTC)
 * Thanks— I should have done it that way in the first place. ---— Gadget850 (Ed)  talk 13:50, 10 March 2010 (UTC)
 * No problem. Was a fun little exercise. PaleAqua (talk) 01:08, 11 March 2010 (UTC)
 * Fun. It has taken hours to work that little template. It has been used in so many odd and wonderful ways. Tables full of fracking dagger symbols that link to different notes. One last article to do... ---— Gadget850 (Ed)  talk 04:39, 11 March 2010 (UTC)

Wireless Application Protocol Bitmap Format
I would add the Wireless Application Protocol Bitmap Format (short wbmp), but I'm not sure if I should add this row to the Mobile Web technology support- or to the Image format support-table. what do you think? mabdul 17:45, 30 March 2010 (UTC)

removed references
Two references are removed about opera support. They aren't outdated or unneeded: I do think everything should become more referenced! Why remove these as facts? mabdul 04:33, 7 April 2010 (UTC)
 * I considered them leftovers from the initial announcements. First off, the ‘references’ in question were directly linked instead of ref'd. If we were/are to put them back, they should be marked up as references.
 * Bittorrent ref: http://web.archive.org/web/20060529044800/http://my.opera.com/desktopteam/blog/show.dml/154823
 * IPv6 ref: http://web.archive.org/web/20060618005359/http://my.opera.com/desktopteam/blog/show.dml/271098
 * Secondly, these are not really references. If we want to reference it, we should google for a third party article. The main reason I bothered to remove them, however, is that Opera is the only* one ‘referenced’, making it look like "yes we support it BUT..." I agree references are good, but in this case they're hardly necessary, as they're not disputed features. Anyway, that's my argument. It was probably a bad idea to say ‘removed references’ in my edit note, as that's not what I consider them to be. *The only other field in that table that's referenced is OmniWeb's Gopher support, but feel free to add proper refs if you feel they're valuable. WOFall (talk) 17:23, 7 April 2010 (UTC)

Bad Table Rendering
I've noticed that at least a couple of the tables on the right of the screen overlap the table of web browsers by year on the left of the screen. It looks to me like someone designed the page in IE and ironically enough failed to do a comparison of how it looked in any other browser. I've tried Firefox in Win & Linux, along with both Opera and a Chrome clone in Windows and the page only looks decent in IE. Maybe someone who knows how to work these Wikipedia tags can fix it because I'm not sure how to. 132.170.67.1 (talk) 18:23, 3 May 2010 (UTC)
 * This could probably be rectified by setting a simple right align on this template. However, I will not do it, as this template is used on quite a few other pages, and I don't want to get yelled at ;) WOFall (talk) 22:47, 4 May 2010 (UTC)

Language Mix Up
In the Internationalisation section, the last language supported by Google Chrome is listed as "Vietnamese (cy)". "cy" is the abbreviation for Welsh, so this needs to be changed to one of these here: N4m3 (talk) 16:32, 15 May 2010 (UTC)
 * "...Vietnamese (vi)"
 * "...Welsh (cy)"
 * "...Vietnamese (vi), Welsh (cy)"

Check version number before editing vulnerabilities
In the vulnerabilities table both Chrome and Safari seem to have been edited to reflect problems that were found in their 4.x versions after the 5.x versions were released. I removed the errors and just wanted to remind prospective editors to make sure to check against the latest version number before editing. 132.170.50.236 (talk) 15:05, 11 June 2010 (UTC)

Per-site security configuration - Chrome
The note on partial support for chrome is "Starting with version 4, Google Chrome can disable Cookies, Images, Javascript, Plugins, Popups, and Geolocation individually." but I fail to see how this is "partial", even from the note it sounds like chrome has supported per-site configuration fully since version 4 (which is even unsupported for being out of date now). Zamadatix (talk) 00:17, 12 August 2010 (UTC)

BMP Image format support
A BMP column should be added to the Image format support table. —Preceding unsigned comment added by 144.136.83.19 (talk) 13:22, 22 September 2010 (UTC)


 * BMP's not useful in webcontent since it's not compressed, and unlikely to be widely used. If it's not widely used, it's not topical TEDickey (talk) 13:24, 25 September 2010 (UTC)


 * But it's one of the handful image formats supported by all major browsers. 144.132.204.79 (talk) 05:20, 28 September 2010 (UTC)


 * ehm, its handful since every application/operating system support that file format. as you can see here that every major browser engine supports that. but as tedickey said: nobody should use this format and there are (png,gif,jpeg,etc) better formats. mabdul 10:03, 28 September 2010 (UTC)


 * This is about browser support, not format desirability. 144.132.204.79 (talk) 12:24, 28 September 2010 (UTC).


 * But we cannot list every feature supported by browsers. We need to exclude little used features to make the article tractable to read and edit. Let's not try to turn Wikipedia into a collection of trivial facts. Let's keep it an encyclopedia, which is a collection of articles that contain the most important information about the topics they cover. -- Schapel (talk) 17:13, 28 September 2010 (UTC)


 * If eight image formats not supported by all major browsers are included, surely one of the four that is shouldn't be left out. I for one came to this article to find out the extent of BMP support. Wikipedia should be, well, encyclopaedic. 144.132.204.79 (talk) 23:09, 28 September 2010 (UTC).


 * Yes, Wikipedia should be encyclopedic, meaning broad in scope or content. Encyclopedic does not mean including every bit of information no matter how trivial. Wikipedia should leave out most information on most topics. BMP is not a commonly used format for web pages. JPEG, GIF, and PNG are the main ones, with APNG, JPEG2000, TIFF, MNG, and SVG occasionally used. I'm not even sure why XBM is listed in the table. -- Schapel (talk) 01:04, 29 September 2010 (UTC)

TEDickey: Actually, the BMP format is compressed using RLE.

Schapel: I use BMP files every day. They're far more common on the web than JPEG2000, TIFF, MNG, or even SVG files. It's definitely worth including in the entry. Ideally, a browser should be able to read BMP files. Not being able to read them would be a drawback and it would be notable for someone not seeing a picture they were supposed to see, right?--Best Dog Ever (talk) 02:43, 29 September 2010 (UTC)


 * It's unlikely that you can provide a WP:RS for the remark. However, some examples of sites using BMP's would be constructive TEDickey (talk) 08:08, 29 September 2010 (UTC)


 * Here are several thousand sites using BMP images: .--Best Dog Ever (talk) 08:19, 29 September 2010 (UTC)


 * That's 12,000 hits. SVG gives 4 million.  We're looking for something that supports your remarks TEDickey (talk) 08:37, 29 September 2010 (UTC)


 * MNG files get 327 hits: . So, that means you're applying a double standard to MNG and BMP. In any case, there are, at the least, thousands of sites using BMP images. And those are just the pages Google knows about. That makes the format notable in this context to me.--Best Dog Ever (talk) 09:07, 29 September 2010 (UTC)


 * Agreeing with you that MNG also is nonnotable trivia, like BMP TEDickey (talk) 09:26, 29 September 2010 (UTC)


 * MNG is little used because there's little browser support. The same goes for JPEG2000 and TIFF. BMP is not widely used despite being supported by every browser for many years. It's not really a double standard. -- Schapel (talk) 11:09, 29 September 2010 (UTC)


 * I think that will change as more people switch from dial-up to broadband connections and from broadband to fiber-optic connections. It will also become more common as hard drives increase in capacity. In the future, image compression will be obsolete. Movies will also be streamed to our computers uncompressed. I have come across BMP images on the web by chance -- yesterday before I came across this conversation, in fact. So, I would be interested to find out which browsers support it and which don't.--Best Dog Ever (talk) 20:32, 29 September 2010 (UTC)


 * BE Bold! mabdul 21:09, 29 September 2010 (UTC)


 * Where is the information being added to the article about BMP support coming from? -- Schapel (talk) 19:01, 1 October 2010 (UTC)
 * Should we assume it is original research because there are no citations for the information? -- Schapel (talk) 12:44, 4 October 2010 (UTC)
 * Couldn't we nearly rate everything as OR since we don't have any reference at the moment? Maybe I / we can start a userfied version of this list and add the references to every cell. mabdul 16:28, 21 October 2010 (UTC)

Charts for Beta Versions
Hmm... Wondering if we can add details for the beta versions; just need to include the date we have tested it, the version and what features are still missing. I'm Using Internet Explorer 9 beta and can help! :D and there are some people (including me) who wants to experience beta versions, and would like to check if it could harm or slow down my computer based on others experience. Well, Good luck! Coleet (talk) 11:47, 21 October 2010 (UTC)
 * Betas are not finished version. these trable are complex enough. If the betas remove again a ferature the confusion is pre-programmed. mabdul 16:32, 21 October 2010 (UTC)

Release Table-template
I have no idea where this comment goes, but the very first table (Web browsers by year) should be corrected to reflect the advent of Chrome 8 in 2010 (right now it says Chrome 4 through Chrome 7). Thanks! - JobiWan144 — Preceding unsigned comment added by JobiWan144 (talk • contribs) 08:32, 13 December 2010 (UTC)
 * I moved you're comment at the bottom of the talk page. next time use the preview option! I willadd the new chromes. mabdul 09:41, 13 December 2010 (UTC)

SecurityFocus information is incorrect?
I see that someone has removed SecurityFocus information from the Vulnerabilities section with the justification that it is incorrect. I've never seen any claim before that the information was incorrect. I think the issue should be discussed before the information is removed. I also see there's a claim that the SecurityFocus information is hard to update. I would agree it's a bit of a pain, but if someone thinks it's too much of a pain to do, they can simply not update it. I have been updating the information and correcting others' mistakes for years. I only ask that if someone wants to update the information that they do it properly, and it they cannot do it properly they can let me or someone else who can do so update it. -- Schapel (talk) 15:40, 17 December 2010 (UTC)
 * I think what the editor who removed SecurityFocus information meant was that the links were wrong on the old versions of browsers he added to the table, and he didn't want to go to the trouble of fixing them. That, I think, is no reason to delete content from Wikipedia. I can fix the links for the browser versions that we reach a consensus on keeping. -- Schapel (talk) 23:36, 17 December 2010 (UTC)


 * Actually, I removed the SecurityFocus information because some of the information listed appeared to be incorrect AND I didn't want to have to update the new additions that I added to the table. =) Let's start with the false positives that I noticed:
 * IE6: If you click on the oldest unpatched link then on solution, you'll see that Microsoft has released a patch for this vulnerability.
 * IE7: Again, a patch has been issued for the vulnerability.
 * In both cases, there appears to be conflicting information on the site; This isn't a complex issue like climate change -- either a patch fixed something it or it didn't -- how can you rely on the information otherwise?
 * When I did a search for vulnerabilities in IE6 SP3 there were ~500 results total; I find it hard to believe that 473/500 are unpatched.
 * There are supposedly 62 unpatched vulnerabilites in IE8, but only 26 in IE7? That seems very peculiar to me.
 * Regarding false negatives, both Safari and Opera have unpatched advisories according to Secunia, but there wasn't anything listed in the SecurityFocus column, which I attributed to difficulty culling the data. IMHO, the SecurityFocus data is inconsistent, far too difficult to cull, and frankly, unreliable.  Personally, what I would like to have added is a column that summed the total number of unpatched days for all advisories for a given product, but since that data isn't readily available, I figured adding statistics on the total number of advisories, number of advisories in 2010 and percentage of advisories that were very critical seemed like a close second place. -- Lhignight (talk) 14:29, 18 December 2010 (UTC)

Java applet support
There are several ways of Java applets support in browsers: full-native (?), using JRE, using plugin (and JRE?), using JDK etc. The article has only the following comment for it: Java support is for built-in support by the browser without the plugin from SUN.. It's not clear for editors (that's why Firefox and IE randomly has Yes while Mozilla has No) and not really useful for readers: they probably need to see the ability of browser to run applets (via pre-installed software, official plugin, 3rd-party plugin etc) rather than core abilities for something not clearly defined (due to copyright issues?).

So I suggest to drop the old rule (about built-in support) for this feature and fill the column with different values for different cases: No (never), Plugin, JRE, JRE+Plugin etc. Or to set for most browsers Yes with footnotes. —Preceding unsigned comment added by 80.70.236.82 (talk) 10:34, 17 January 2011 (UTC)


 * Browsers have two ways of supporting Java -- built-in support and using the Java plugin. The possible options would be No, Built-in, or Built-in and Plugin. But all browsers that support plugins would support Java using the plugin, so it's not really making a comparison between different browsers, which is the point of the tables. I think that's why the options are No and Yes (builtin). We should really save footnotes for exceptional cases, not the common case. -- Schapel (talk) 14:46, 17 January 2011 (UTC)


 * Are there really two ways of supporting Java? Here is my little OR (i.e. copypasting official documentation):


 * Opera for Windows: For Windows, Opera uses the Java plug-in to run Java applets. If you do not have Java installed, Opera will automatically offer to take you to a download site when you encounter such content. To install Java, go to the Java website and follow the instructions. (c)
 * Opera for Linux: Sun Microsystems (now part of Oracle) created the Java programming language, but most Linux distributions will include a default Java implementation that was not created by Sun/Oracle. (c) The Java plug-in is part of the Java Runtime Environment (JRE), but Opera does not use the plug-in: it uses the JRE directly. To get Java working with Opera, you must install the JRE, and configure Opera with the correct Java path.  (c)
 * Internet Explorer: Microsoft no longer ships Java with Windows, and in recent versions of Windows, Internet Explorer cannot support Java applets without a third-party plugin. (c) To run Java programs in Internet Explorer, however, you must install special Java software. (c)
 * Firefox/SeaMonkey for Windows/Linux: Before Firefox can run Java applets you must have the Java Runtime Environment (JRE) properly installed and enabled. Starting in Firefox 3.6, you also need the new Java plugin ... (c)
 * Firefox/SeaMonkey/Camino for Mac OS X: Java Runtime Environment that ships with OS X has major issues as a plugin for Gecko-based browsers. As such, mozilla.org has opted to include the Java Embedding Plugin by default in all of its projects. (c)
 * Chrome: On Windows, Mac, or Linux? Google Chrome supports most popular plug-ins, including Adobe Flash Player, Adobe Reader, Java, ... (c)
 * Safari for Mac OS X: Enjoy running Java applets on the web thanks to Java support in Safari. (c) (no plugin, just JRE?)
 * Safari for Windows: For a richer browsing experience, you may want to install the following plug-ins: ... Java (c)
 * Konqueror: The Java support relies on the KDE Java Applet Server( KJAS ) ... You do not need a complete JDK for KJAS to work- you just need a JRE. (c) (no plugin, just JRE and KJAS)
 * The Java Plug-in: Java Plug-in enables applets written to the Java SE Platform 6 specification to be run in Mozilla and Internet Explorer web browsers. Java Plug-in comes with the 6 JRE/JDK. (c)


 * Therefore these two ways are about the same for users: using a 3rd-part JRE directly or using a 3rd-part JRE through the plugin supplied with JRE. Compare with 3rd way in Nexus: it has never had the Java support and has the same No in table as modern browsers. —Preceding unsigned comment added by 80.70.236.82 (talk) 17:01, 17 January 2011 (UTC)


 * The only browsers I can see that you're saying work without built-in or plugin support are Konqueror and Opera. I can't load the page you gave for Konqueror. The page for Opera you list states Opera uses the JRE directly, but only on Linux. If you'd like to add a footnote that Opera on Linux uses the JRE directly and not the plugin, that's fine. I'll change the table to reflect that IE no longer has built-in Java support. I'll also remove the from SUN qualification from the statement about Java plugins, because there are plugins from other sources now. -- Schapel (talk) 14:52, 18 January 2011 (UTC)


 * Now You can see the nonsense of this approach: all browsers has No excluding Safari with a noted restriction. Would You use the same without-a-plugin rule case we add the Flash support column? —Preceding unsigned comment added by 80.70.236.82 (talk) 07:57, 19 January 2011 (UTC)


 * No, because no browsers support Flash without the plugin. It would be silly to have a Flash column for this reason. We do it for PDF support, because some browsers do support PDF without a plugin. The article seems to be consistent with the way it compares browsers. If you have some sort of rationale for changing the way the tables in the article are constructed, let's have it. -- Schapel (talk) 17:06, 20 January 2011 (UTC)


 * That's about data, not tables. The article is for users, not only compare geeks like us. I believe they do interested in the ability of using a feature rather than in internal support details. Having some JRE preinstalled (most cases) user can install a modern browser and have the Java support enabled without extra fuss (because of Java plugin supplied with JRE). Or he can install a not so modern browser and get no Java support at all. Why would he need a table with No for all these cases?
 * My suggestions are higher: drop the native support restriction and check the ability of browser to run Java applets with JRE installed. Does it (pre)installed or not depends on the OS (incl. release version). Some browsers require an additional plugin instead of the "Java Plug-in" from JRE and should be marked accordingly. —Preceding unsigned comment added by 80.70.236.82 (talk) 09:18, 21 January 2011 (UTC)

Disputed Acid3 Sources
I've disputed the claim that Chrome and Safari pass Acid 3 having repeatedly asked for a reliable source for this claim, including a user page discussion and have been meet with a mixture of diversions on the subject. With no reliable source forthcoming after multiple requests it brings to doubt if there are any, so, I have marked the section as 'factual accuracy is disputed.'. Regards, SunCreator (talk) 01:48, 2 November 2010 (UTC)


 * Considering I could not find discussion of the topic on your talk page, nor on the google chrome talk page, I can't vouch for any discussions you've had elsewhere (I can't find them). However, as on the Google Chrome page there is a link to the official chrome releases blog here which outlines Acid 3 compliance. Sylvanelite (talk) 10:46, 4 November 2010 (UTC)


 * Thanks for your reply. The discussion has been both in the edit summary and on the reverting editors talk page. The source you supplied is the best yet suggested, unfortunately the Chrome blog is not a reliable source but a self published blog, same issues of not being a reliable source applies to the Apple blog for the Safari browser. Regards, SunCreator (talk) 14:44, 29 November 2010 (UTC)
 * Self published information by corporations is generally considered a reliable source whether it is in blog style or web page style. What matters, whether its a corporation or individual, is are they an expert on the subject.  I think google can be considered an expert on whether their browser passes Acid 3 tests.  Doubly so, since google was the main developer of Acid 3 tests. :)   Daniel.Cardenas (talk) 16:43, 29 November 2010 (UTC)
 * Self-serving promotional claims are rarely considered an acceptable reliable source but I'll let others comment. Please raise the issue on WP:RSN. Regards, SunCreator (talk) 17:05, 29 November 2010 (UTC)
 * Do you have an example of corporate published info not considered a reliable source? Anywhere you look corporate info is used as a reliable source throughout wikipedia. Daniel.Cardenas (talk) 05:34, 30 November 2010 (UTC)
 * Are we looking at the same Wikipedia? By definition such sources are not independent, and they are (or should be) treated with great care. Drmies (talk) 05:35, 30 November 2010 (UTC)
 * The information is from their official website, and as no company is not going to flat-out lie about something that easy to check, it should be regarded as reliable and true until proven otherwise by a reliable source.-Zyrath (talk) 04:31, 11 December 2010 (UTC)
 * Oh, I'm happy someone noticed it too. I can confirm that on my computer, Chrome gets 100/100 but fails the test (#26 and #69, like Opera). Does the result change if you use another computer? Shouldn't the information be changed? -Zaba 17:26, 13 February 2011 —Preceding unsigned comment added by 80.11.199.18 (talk)
 * First, you're doing original research which is not allowed in Wikipedia; you need to have a reference to a reliable source. Second, I suspect that you're not running the Acid3 test on a reference computer as you are supposed to for the performance aspect of the test. Third, we have confirmed that Chrome's official blog is indeed a reliable source. So, no, the information should not be changed. -- Schapel (talk) 16:43, 13 February 2011 (UTC)

Spatial navigation feature of web browsers
As the creator of TVFriendly, I have conflict of interest regarding this article, so I leave the decision whether to include this adding up to others. The adding that I am suggesting is about the (absence of) Spatial Navigation feature in IE and in Firefox that can be achieved by using an extension like: TVFriendly (www.tvfriendly.com). In the table: “Accessibility features (continued)”, in the rubric for the feature “Spatial Navigation” – for the: “Mozilla Firefox”, It is written “No” with a note [note 14] that tells about some special Firefox builds with the spatial navigation features. I think that it can be more informative if the note will tell also about the extension. Sincerely, Tal Talbob (talk) 16:47, 2 June 2011 (UTC)

Web-gl support
Web-gl should be added in the list for comparison. 83.108.198.50 (talk) 20:37, 12 July 2011 (UTC)


 * would you bother elaborating on adding yet another security hole? — Preceding unsigned comment added by 85.130.6.148 (talk) 00:12, 23 July 2011 (UTC)

Why so many old versions of browsers in Vulnerabilities?
The Vulnerabilities table is huge now that so many older versions of browsers have been added. I can understand IE 6, IE 7, and IE 8 in the table because they are all supported and in common use. I can understand having Firefox 3 and Firefox 4 in the table after Firefox 4 comes out while both versions are supported and popular. Perhaps sometimes we can have two versions of the other browsers, again just after a new version comes out and both old and new versions are popular. But the last three versions of Chrome? The past three versions of Opera? The past four versions of Safari? Why? Many are no longer supported, so they are not getting vulnerabilities fixed. Many of those browser versions are barely used any more, so information about the vulnerabilities in them isn't very useful. If someone wants to look up that old information, they can always go to Secunia and SecurityFocus and look it up. -- Schapel (talk) 12:33, 17 December 2010 (UTC)


 * Regarding the size of the table, I don't believe that it is either huge or too large. It is still smaller than most of the other tables on this page and the actual browser data just fills a single screen on my laptop.  However, I do believe it is larger than necessary due to the formating of the "{{start" template(?).  The table is mostly blank/whitespace because of it.  If there was a way to shorten the output so instead of "December 10, 2010;" it produced "Dec 10, 2010;" then we could either move the number of open advisories onto the date line or bring the "8 days ago" information up to the date line saving quite a bit of vertical room (~30%).


 * I included the additional browsers/versions because they are being used (more than you would expect anyways) based on metrics obtained from Netmarketshare and W3Counter (the same metrics utilized in Usage share of web browsers). For example, Chrome versions 6 and 7 are in greater common use than version 8, so I included them  (would you prefer that version 8 be removed instead?).  FF 3.5 and 3.0 are both in the top 10 list on the W3Counter, and according to the Netmarketshare, FF2 is nearly as popular as Chrome v6.  Safari 4 and 5 were included because they're also in the top 10 list at W3Counter.  I included Safari 2 and 3 because people using older versions of OS X are not able to upgrade to the latest version of Safari (similar to WinXP/IE6);  However, in hindsight, I do agree that both of these versions should be removed.  Opera version 9 and 10 are still in greater use than version 11.  Also, I removed Seamonkey because it doesn't appear in any of the metrics.  Currently, there are 17 browsers/versions in the table, removing Safari 2 and 3 would bring that down to 15.  Personally, I feel that removing Chrome 6 and 7, for example, is robbing people of potentially valuable information, and hopefully, it will encourage more people to upgrade (and many clearly aren't based on the metrics). -- Lhignight (talk) 13:41, 18 December 2010 (UTC)


 * I think the latest version of browsers should always be included in the list, so no, I would not argue that Chrome 8 be removed. The statistics you list are from November, so of course Chrome 8 was not used much then, as it was released in December. This is also why Chrome 7 is popular in the stats you cite -- Chrome 7 was the latest version in November. I think the first thing to realize is that the data you're using for your argument is outdated. I can understand having Chrome 7 on the list while it's supported and popular, in addition to Chrome 8. Similarly, Opera 11 was recently released, but I can understand having Opera 10 on the list while it's still supported and popular. I can understand having Firefox 3.5 on the list because it's supported and popular. I can understand having Safari 4 on the list while it's supported and popular.
 * As for Chrome 6, Firefox 2, Opera 9, and Safari 2 and 3, those are quite old, not used much, and I don't think supported any more. After browsers are not supported, it seems that security vulnerabilities are not reported against them any more. I don't think even Firefox 3.0's vulnerabilities are updated any more; it's inconceivable to me that no security vulnerabilities were discovered in it since Mozilla stopped supporting it about a year ago. The data for these old, unsupported versions are not reliable for this reason. I would recommend removing these older versions form the table to make the data more reliable and reduce the size so it can be read more easily. Nearly all the tables in this article are huge and nearly unreadable. I think this should be fixed by making the unreadable tables more readable, not making one of the few still readable tables also unreadable. -- Schapel (talk) 14:37, 18 December 2010 (UTC)

funny, since when IE is insecure? safari wont even start if you have mandatory DEP/ASLR on, same with chrome though i dont have the courage to touch it nowadays — Preceding unsigned comment added by 85.130.6.148 (talk) 00:19, 23 July 2011 (UTC)

Browser stats conflict
Being a web developer, nearly everyone I know goes by w3schools as the best browser stats, which completely disagrees with your data. Did Microsoft pay you guys under the table or what, lol? I hope you review the best source for stats, http://www.w3schools.com/browsers/browsers_stats.asp — Preceding unsigned comment added by 68.183.149.24 (talk) 17:24, 27 September 2011 (UTC)


 * Those stats are only for the w3schools server itself. The stats for that site are not typical, because the visitors are not typical users. You can find more explanation at usage share of web browsers. Oh, and assume good faith. Thanks. -- Schapel (talk) 18:53, 27 September 2011 (UTC)

Mobile browsers missing
Browsers like iOS Safari (different from desktop Safari (web browser)) and Android (operating system) browser are missing. They share the same rendering engine (WebKit) but the user interface is quite different. — Preceding unsigned comment added by 88.27.29.10 (talk) 10:20, 7 September 2011 (UTC)


 * Yeah, the should create a Comparison of mobile web browsers, but starting a new page is highly hard since we should start another comparison with unreferenced facts (in my eyes). we should only create (new) pages with references for ALL features... (in my eyes). mabdul 19:30, 27 September 2011 (UTC)

Do they or don't they support Java?
I'm looking for comparative info browser-to-browser. I cannot find any USEFUL info about Java support. Is this because too many people are firmly welded to Wikipedia conventions? GET OUT OF THE SQUARE. As it stands, this page is useless to me and many others. The comment above from Schapel on 14:46, 17 January 2011 (UTC) in Java_applet_support is not helpful, it sidesteps the object of an encyclopedia, which is to give or clearly reference all available information. So, does any given browser support Java in any way at all, or does it not? 122.200.166.205 (talk) 02:53, 30 December 2011 (UTC)
 * No, the object of an encyclopedia is not to give or clearly reference all available information. There are many things that Wikipedia is not, including an indiscriminate collection of information, which you seem to think it should be. As to your immediate need, to get Java, you install the Java plugin and then Java works. -- Schapel (talk) 13:10, 30 December 2011 (UTC)

Page saving formats
The "html" format of a saved web page creates a hierarchy of folders and files. The "mht" format saves the web page as a single file, allowing easy storage, management and mailing. I believe this feature is key to the use of a browser. Would it be possible to include this in the comparison? AndreasMD (talk) 09:30, 16 April 2012 (UTC)

Internet Explorer is freeware?
In case anyone is interest in joining in, there is a discussion of whether Internet Explorer is freeware at Talk:Internet_Explorer_9. I know we've discussed the matter here a number of times, and have always reached the conclusion that it's proprietary software because it requires a license from Microsft to run. -- Schapel (talk) 14:14, 27 August 2012 (UTC)


 * Then someone ought to rewrite Freeware, to pointedly exclude IE (and a few others), so that they're not applying the category inconsistently. TEDickey (talk) 21:29, 27 August 2012 (UTC)
 * May be you could elaborate your comment? Preferably at Talk:Internet Explorer 9. — Dmitrij D. Czarkoff (talk) 21:54, 27 August 2012 (UTC)


 * The beginning of Freeware summarizes its scope in terms very close to the comment which started this discussion. Lacking the pointed exclusion, some readers will disagree with the "always reached" aspect of the comment TEDickey (talk) 22:22, 27 August 2012 (UTC)
 * FWIW the I will disagree with "always reached" aspect anyway. The only discussions concerning the cost of IE is Talk:Comparison of web browsers/Archive 1, which ended with cost "0" with a note and statement that the whole "commercial IE" thing is invalid (though IE wasn't available for download back then). — Dmitrij D. Czarkoff (talk) 22:37, 27 August 2012 (UTC)

Too long
This article is far, far, too long. Something needs to be done about this. Now.-Zyrath (talk) 04:35, 11 December 2010 (UTC)
 * any examples? What do you think? I do think everything is fine... <b style="font-family:Courier New; display:inline; border:#009 1px dashed; padding:1px 6px 2px 7px; white-space:nowrap; color:#000000; font-size:smaller;">mabdul</b> 09:40, 11 December 2010 (UTC)


 * Like (almost) any of the comparison-of topics on Wikipedia, a large fraction of the content isn't really interesting to most readers. However, pruning it seems hard.  Splitting it into manageable-sized topics is probably the way to go. TEDickey (talk) 13:07, 11 December 2010 (UTC)


 * What do you ave in mind? I think we could remove (although I don't think that this would be a good idea) the web (/Internet) standards parts (except the protocols) because these parts are already handled in the comparison of web browser engines-series and the reader has only to translate the engines with the corresponding browser. Would this be manageable and satisfy solution? <b style="font-family:Courier New; display:inline; border:#009 1px dashed; padding:1px 6px 2px 7px; white-space:nowrap; color:#000000; font-size:smaller;">mabdul</b> 14:06, 11 December 2010 (UTC)


 * Maybe a good thing to start with is to move off (separate article?) all the browsers whose development has been discontinued.--DeTru711 (talk) 00:57, 16 June 2011 (UTC)


 * I think this article can be split into two separate articles: "Comparison of Discontinued Web Browsers" and "Comparison of Modern Web Browsers". – ShiViMan (talk) 20:16, 18 September 2011 (UTC)
 * I support this initiative.1exec1 (talk) 09:14, 21 September 2011 (UTC)
 * I moved the sections on web browser history to the article web browser history. -- Helena srilowa 01:06, 28 August 2012 (UTC)

article is useless because it is totaly cluttered

 * it does not present relevant information in an useful way

It seems like its only scope has become to push the already established browsers. For example, why are the Usage share of web browsers and Web browser history both at the beginning of the article? The usage share is very interesting information, but given that the article starts with a lot of historic blabla, the usage share belongs further down the line and not at the top!

To de-clutter this article I suggest to outsource ALL stuff that is not related to browsers currently being in development to a separate article and simply link to it. Then I would restructure the entire article, like say:


 * 1) software being in current development vs. abdandonded/historical projects (link);
 * 2) Operating System support and mobile variant (in case you want to use the same browser on desktop and smartphone)
 * 3) FOSS software or proprietary software
 * 4) If FOSS, then which License IF proprietary then what is the fee/cost
 * 5) Layout engine and UI toolkit, luckily List of web browsers for Unix and Unix-like operating systems makes the search for this features easy because this article does not. But why isn't there at least a link to that article???
 * 6) core features I (note that most of these already depend entirely on the layout engine and its version!!!): HTML4, HTML5, CSS2.1, CSS3, ACID-Test-Results, etc.
 * 7) core features II (note that most of these already depend entirely on the UI toolkit and its version!!!): ???
 * 8) core features III: anything that does not depend on layout engine or UI toolkit
 * 9) extra features
 * 10) other features
 * 11) usage share of
 * 12) Layout engines
 * 13) browsers

One more time: The fact the the usage share and the Web browser history both are both right at the beginning of the article bothers me. Its wrong and biased towards pushing established browsers. Doors5678 (talk) 12:15, 25 March 2012 (UTC)


 * Replies per point:
 * Very rarely the browsers are explicitly deprecated. Most of them, including those last released in 1994, just stopped being publicly maintained; thus the "active/abandoned" split is practically difficult and potentially controversial.
 * Operating system support: agree, mobile and desktop OSs should be put together in one table
 * FOSS/proprietary: agree
 * Features:
 * Standard support is potentially messy, unsourced and difficult to follow; ACID results are not features at all. BTW, if we name layout engines, why should we at all compare the engines features here? There is a comparison of layout engines.
 * "???" – must have!
 * So, as core features I section consists only of "layout engine" and "UI toolkit", may be we can merge core features III there?
 * Extra features: these are somehow different from previous part?
 * Other features: were they not supposed to be covered in core features N
 * Usage share of — we have an article on this, no need for separate section
 * P.S.: the thing you call "pushing established browsers" on Wikipedia is generally called giving due weight according to the sources.
 * Dmitrij D. Czarkoff (talk) 13:16, 25 March 2012 (UTC)


 * core featues I yes, simply link to the extra article Comparison of web browser engines (and make that article usefull...sigh)
 * the core features II and the core features III: yes, could be merged. E.g. I am not sure whether extensions like "epiphany-extensions" which are written in C, or the mozilla/firefox-plugins, which are written in JS both depend on the UI toolkit. Availability of extensions/add-ons/plugins is definitely worth mentioning ;-) One typical core feature II is the e.g. GNOME Keyring or the Spell checker. Mozilla brings its own spell checker, other browsers use the one already integrated into the system.
 * It would be astonishing if the WP was being utilized in the ongoing browser-war...). However, since there already extra articles, excelent, lets remove the pie-chart right at the top of the article and simply link to that other article: Usage share of web browsers instead. The information is a) still there, b) easy to be found and c) does not dominate that article any longer.
 * So, do you disagree with me, that the article is totaly cluttered? That information is not presented in usefull way? — Preceding unsigned comment added by Doors5678 (talk • contribs) 09:17, 27 March 2012 (UTC)
 * Toolkit dependencies: neither plugins nor extensions are toolkit-dependent. Instead they depend on respective APIs which are generally toolkit-independent in case of plugins (at least there are Qt and GTK-based NSAPI plugins). Plugin API support is typically engine features (with Google's API being a notable exception, though number of available plugins is extremely limited); extensions are typically supported on per-browser basis (clones normally share mainline browsers' extension APIs). Information on extensions is normally very hard to source, so I can't imagine extension-related comparison that would be reasonable in size, useful and sourced. GNOME Keyring and Spell checker are engine-related features. At least I'm not aware of browsers implementing these features; Mozilla uses MySpell BTW. Pie chart is where it should be, please leave it alone: it is the only objective piece of comparison on this page.
 * I totally agree that this article is cluttered. Still I sincerely believe that it can't be uncluttered, as it is completely impossible to compare, say, Internet Explorer, Epiphany, Abaco and Lynx in a meaningful way (apart from usage shares, of course). — Dmitrij D. Czarkoff (talk) 11:55, 27 March 2012 (UTC)
 * If it is quote: "completely impossible to compare" mentioned browsers, and also, since there already is an exta article for Usage share of web browsers, what is the f*cking point of this article here??? You present valid arguments, but you are not willing to act on them. For obvious reasons I prefer a web browser that uses the same spell checker, that my office suite, Email client, etc. use. But how to find the ones that do or at least can be conigured to to? I could imagine, that people who don't just passively browse the web but also create own content, would prefer such a functionality and information on it. And I am sure, there are other examples besides the spell checker. Nobody? Doors5678 (talk) 17:14, 27 March 2012 (UTC)
 * I moved the sections relating to web browser history to the article web browser history (talk page). That ought to add a little breathing room. -- Helena srilowa 01:04, 28 August 2012 (UTC)
 * Many of the browsers in the tables are no longer around. It would be good if all the historical (obsolete browser) info. could be moved to the history article, but that's a lot of work. It might be an idea to add a hatlink to the historical article. LittleBen (talk) 04:21, 28 August 2012 (UTC)

Unicode equivalence search feature
It seams that Unicode equivalence search feature is not taken into account in this "Comparison of web browsers" when it is an interesting feature. At least a line should describe this feature exist, even if we do not provide a full list of how web browser handle it en tout ou partie. http: //xahlee.info/comp/unicode_browser_char_equiv.html — Preceding unsigned comment added by 86.75.160.141 (talk) 21:17, 20 November 2012 (UTC)

SecurityFocus
The SecurityFocus data in this article is useless at this point. All the links in this article point to versions that are not in the SecurityFocus database, so it's incorrect to use them as references for 0 vulnerabilities. When I went looking for the latest versions of the browsers, they are not listed at SecurityFocus. I think it's time to remove the SecurityFocus column. -- Schapel (talk) 17:10, 16 December 2012 (UTC)

Sort by Date
Forgive me if this has been suggested before or is a commonly known problem elsewhere on Wikipedia, but I think it would be much more useful to be able to sort the list of browsers by release date instead of 'version'. I'm pretty sure that many people don't want to use old browsers but it's hard to see which are recent. Thanks. Flizzjkzaop (talk) 13:01, 31 May 2013 (UTC)

Colors
What is the significance of the colored table headers (rh2 vs. rh) being used for, e.g., AOL Explorer? No explanation is given in the article, AFAICT, and looking at the template documentation doesn't give any hint as to why it's used here. - dcljr (talk) 23:40, 25 June 2013 (UTC)
 * These appear to be browsers that have been discontinued. —WOFall (talk) 22:29, 26 June 2013 (UTC)

Worldwide combined web browser market share wrong
If you guys have a look at http://arstechnica.com/information-technology/2013/06/internet-explorer-10-takes-chunks-out-of-ie9-windows-8-closes-on-vista/ you'll see that IE holds 49.65 of the world's combined (desktop and mobile) web browser market share.

What then does the "Usage share of web browsers according to StatCounter." screenshot refer to?

I think that image should be replaced with one similar to the one on ArsTechnica.

It's all acording to netmarketshare.com on ArsTechnica.
 * « What then does the "Usage share of web browsers according to StatCounter." screenshot refer to? »
 * http://gs.statcounter.com/#browser-ww-monthly-200807-201307
 * See also Usage share of web browsers. There are reasons for measurements to vary, but I personally consider NetApplications's stats to be particularly questionable. —WOFall (talk) 02:58, 8 July 2013 (UTC)

Browser Privacy Policy
One of the most important aspects of browsers is missing, and that is Privacy. I'm not referring to "Privacy Mode" (which keeps your browsing private from other users of your computer and is included in the comparison), but rather to keeping your browsing private from external 3rd parties - notably the browser developers. For example - chrome sends detailed info of your browsing habits to Google - while chromium does not. Could be worthwhile to add it. — Preceding unsigned comment added by 84.228.153.215 (talk) 06:15, 27 July 2013 (UTC)

IE voice control
Hi! I think internet explorer should have "partial" instead of "no", since, if running windows vista, you surely can control the browser with your voice!213.64.150.116 17:05, 16 April 2007 (UTC)

Addition of encoding support table?
One thing that is a good idea to have is a table on encoding support (Unicode and legacy encodings), which would probably go on a separate page due to size issues. This is useful because support on encodings is very different between browsers (for example, IE is the only browser with ISCII support) still need to test this -- Prince Kassad 18:06, 26 October 2007 (UTC)
 * If you can find any reliable sources, why not... --Grey 15:44, 27 October 2007 (UTC)
 * I strongly support this request. Maybe even extending it to a table with 'http' support indicating supported Content-Types (gzip, deflate, etc) and charset (UTF-8, Latin-1, etc). —Preceding unsigned comment added by 84.198.72.247 (talk) 11:48, 30 December 2008 (UTC)

-AdBlock
It kinda bugs me that Firefox has "no" under "ad filtering" when everyone uses AdBlock. Should this and some other entries be changed to something like "via plugin"? 75.152.220.162 (talk) 09:42, 21 May 2009 (UTC)


 * It says so with a note but it would be a good idea to prominently show them different. Platonides (talk) 21:05, 9 June 2009 (UTC)


 * Why does all the browsers that filters ads with a plugin have no with a cross, except firefox says yes with a cross, shouldn't it be a no as well? 72.218.100.143 (talk) 08:19, 8 January 2010 (UTC)

Epiphany (GNOME Web Browser) should definitely say "yes" for ad filtering under "accessibility features"! It's not the same as with Firefox, because here you certainly HAVE the filtering option "out of the box", installed with the browser itself, no need for downloading any add-ons. OK, you can remove epiphany-extensions package, but there is no GNOME-release coming without that, so it's practically included... Arpadapo (talk) 09:02, 24 February 2010 (UTC)

I added a hyphen to the title of this section as without it the title did not display at all and the link from Contents did not function. Could see no reason for this in the "code" LookingGlass (talk) 08:09, 18 August 2013 (UTC)

Single document interface
How do I know whether a browser supports SDI? All I see is a column about tabs, which says "Yes" even when they are optional (such as for K-Meleon). 89.244.102.207 (talk) 10:46, 15 May 2013 (UTC)


 * Agree. I want a browser that has the feature of allowing me to never have tabs.  (I don't care whether this is by having no tab support at all, or by having an enable/disable tab setting.)  It seems like the "tabbed browsing" section should have multiple options:  yes, no, optional, and footnotes for variations like having an add-on that enables or disables tabs, partial ability to disable tabs, et cetera. Jordan Brown (talk) 07:45, 12 September 2013 (UTC)

Browsing History
I notice that there is no information about the topic of browsing history. On this page there is an oblique reference to "full text browsing history search", but do all these browsers really keep a basic type of browsing history (i.e. links visited)? This is a current topic, as some browsers have recently implemented modes that do not keep browsing history (e.g. Chrome's Incognito Window and IE's InPrivate Browsing). Is "browsing history" a feature of most browsers, is it notable enough to mention in the Web browser page, and if so, should a comparison of each of the browser history functions be included in a table here? Twocs (talk) 01:49, 31 July 2009 (UTC)

I suppose Google Chrome no longer supports full text history search. A brute force title search has taken its place since one of the recent updates. Details in https://code.google.com/p/chromium/issues/detail?id=247418 --130.126.59.191 (talk) 21:16, 23 September 2013 (UTC)

Acid3: Not passed / 100/100
Opera (for desktops) has been listed on Acid3 as not passed with an otherwise perfect score. It has rendered the test correctly for the last few versions (at least with me). The rendition is normally smooth and fast here. Is there something important that fails Opera, or is it just an old forgotten update? 158.37.73.13 (talk) 00:31, 20 March 2010 (UTC)
 * As far as I know, it still doesn't pass the performance aspect. Does the report say that no subtests take more than 33 ms? Are you running the test on a laptop? If both answers are YES, then perhaps it passes. On the other hand, we can't add that information to the article because it's original research. -- Schapel (talk) 00:55, 20 March 2010 (UTC)
 * I am running it on a laptop (HP dv9575eo/Win7), and test 26 and 69 usually come out less than perfect. But it generally does the test better than Chrome here, which is said to pass it perfectly. Here's a screen-shot of the shortest of around thirty tests ran February 17 (only six ran for IE): ImageShack. I know it's not statistically significant, but Chrome has not consequently ran the test better on this machine. 158.37.73.13 (talk) 01:43, 20 March 2010 (UTC)
 * From the screenshots shown, Chrome does better on the performance aspect. It ran test 26 in 43 ms, compared to over 100 ms for Opera. It is not the total time (speed of animation) that is the issue, but time for each subtest (smoothness of animation). -- Schapel (talk) 01:55, 20 March 2010 (UTC)
 * Though, the total time used calls for a better test than the fact that one single test is a bit slower or faster, does it not? Chrome might be fast on that specific test (but not faster than 33 ms as stated as perfect earlier), but the total time says that other tests added up to 1150 ms slower than Opera (in the quickest of all the tests). The 62 ms difference in a single stress test is small compared to the total. Why does Chrome pass when it never scored less than 33 ms on test 26 in any of my tests? Is a single lucky pass on any one system all that is needed for a browser to pass it? I would think it had to be consistent. Would be nice to get some different views or clarification on this - I'm no expert in the area.
 * For reference: the above tests were done on a fresh OS with unmodified browsers. 158.37.73.13 (talk) 02:41, 20 March 2010 (UTC)
 * But it's not up to you or me. The creator of Acid3 said it is the smoothness that matters -- each test must complete within 33 ms or less on the reference hardware. Did you run the test on the reference hardware -- a top-of-the-line Mac laptop? -- Schapel (talk) 03:35, 20 March 2010 (UTC)
 * A "top-of-the-line Mac laptop" is not a specific system. Acid3 was created in 2007, and 3 years is a huge amount of time in technology. I've stated my system earlier in this thread, which was a fairly top-of-the-line laptop back then., and Chrome does not pass for performance. Opera even has different versions running for Windows and Mac. The test should not only be valid for Macs when used in the context of this article. Should that not be stated to begin with, otherwise?
 * I don't mean to directly question the validity of the Acid3 test - I believe it's a good test, but while Opera performed better in my testing, Chrome passes because of what can be seen as unreasonable test requirements. I am sorry for singling out Chrome versus Opera, but those are the browsers I can personally reference. 158.37.73.13 (talk) 04:17, 20 March 2010 (UTC)
 * If your was a top-of-the-line laptop a few years ago, it would stand to reason that a top-of-the-line laptop of today would be more than 30% faster and not more than three times faster. That would mean that Chrome would pass the performance aspect and Opera would not. Your tests seem to verify what our sources say. -- Schapel (talk) 13:41, 20 March 2010 (UTC)
 * @158.37.37.13 - Please feel free to question the validity of the test all you like, it was created by an individual, and not an organisation or collection of peers, so it is by its very definition biased. The performance aspect is widely regarded as being preposterous and the creator of the test himself has actually stated that for Acid4, one of the requirements be: "no performance stuff as part of the test" . However, it is not within Wikipedia's purview to comment on the validity or perceived bias of what it documents (doing so would likely violate NPOV guidelines).
 * Also, the reference hardware is not a 3 year old top-of-the-line Macbook, it's defined as "whatever the top-of-the-line Apple laptop is at the time the test is run" - this means even figuring out what the reference hardware is is a completely unscientific moving target, to make matters even more unreasonable.
 * @Schapel I'm not sure how your interpolation of Opera's vs Chrome's results on a modern PC Laptop works, but given Opera performs the test more quickly than Chrome in the tests in the linked screenshot, surely it would also do so on a new laptop. Either way though, this is moot unless the tests are run on a bootcamp Windows install - otherwise, as far as the test is concerned, a stable build of Opera 10.50 does not exist. <sub style="font:bold 14px arial;color:#f27;">ɹəə pıɔnı  02:03, 21 March 2010 (UTC)
 * I'm sure Opera performs the whole test more quickly than Chrome, but Chrome performs the test more smoothly than Opera. Each subtest must complete within 33 ms, and because Chrome takes at most 43 ms per subtest on a 3-year-old laptop it seems reasonable that it would take less than 33 ms on a new 2.66 GHz Intel Core i7. Perhaps we should make a composite image of Opera's rendering and the report given in the screenshot above and use it to demonstrate how you can tell whether a browser passes the performance aspect of the test in the Acid3 article. People don't seem to understand how to interpret the report. -- Schapel (talk) 12:59, 21 March 2010 (UTC)
 * For me both Browsers stop too long on 69 and the rest goes rather fine —Preceding unsigned comment added by 60.240.237.227 (talk) 20:42, 2 April 2010 (UTC)
 * You need to run the test on the reference platform to know if a browser passes the performance aspect. -- Schapel (talk) 18:16, 4 April 2010 (UTC)
 * What do you mean reference system. Also Opera clearly passes with the same results as WebKit based browsers, this section of the article is clearly biased towards WebKit as Opera clearly passes with the same results (Core i5 based system) as any WebKit browser, Opera also performs the test faster. I will be changing this to yes as most browsers seem to have the same problem and still receive a yes. Also I can list my exact specs if you care that much as this is a PC I built. (EDIT) I have also noticed that the Opera Version does appear less smooth this is in fact due to the fact that some tests are running faster than others as where webkit I believe may have some smooth enabled, but this is irrelevant as the performance is still valid smoothness is insignificant where as the test is really asking for the performance to be Under 33 MS. SandySoup (talk) 03:03, 23 April 2010 (UTC)
 * You need to run the Acid3 test on a top-of-the-line Apple laptop. Opera clearly does not pass the performance aspect of the test. It does not matter whether Opera performs the entire test faster. It must perform each subtest within 33 ms on the reference platform to pass the test. This section of the article is not biased in any way that I have observed. In any case, all you need to do to state that Opera passes is to find a reliable source that states that Opera fully passes Acid3. We cannot use the results of your test as that would be using original research. Go ahead and read this entire thread for all the gory details. -- Schapel (talk) 21:35, 23 April 2010 (UTC)
 * Where did you get that from because using the term top-of-the-line Apple clearly implies bias either on Wikipedia's part or Acid's part. I am more inclined to believe it is Wikipedia which is biased as I ahve never heard of a Reference System (FYI Yes I have searched it up and came up with nothing related to Top of the Line Mac). Second of all what defines top of the line is different and can be argued, (EG My friend believes his Core 2 Duo mac is top of the line). Finally it should be Windows with a minimum hardware or even better any OS as Windows is used by most people not Mac OS X based Computers. Please stop this bias in favor of WebKit. Using Mac OS X applies only to 5- 10 % of all computer users versus Every other OS which applies to 90 - 95 % of all PC Markets. Opera had it first and the Wikipedia page on Opera clearly states that an internal Dev Build of it had passed Acid. So please tell me where you got this magical reference system information from. (Edit) Also where does it mention that the Computer had to be running Apple based Software and we can assume since its performance requirments are theoretically (As far as I am Believing) for a top of the line mac that a computer who has lower specs is irrelevant or better as it shows that the web browser can run as fast to pass acid on a slower system. (Edit 2) Should the Acid Team have listed Top of The Line Mac as their reference system then the entire integrity of the test should be questioned as it shows that the test makers believe a top of the line Mac is better for Web Browser tests than a custom built Linux based computer or a Dell, HP computer and this section should be question and removed as that shows the entire test believes Apple based technologies are better than other companies. (Edit 3) When the developer of Acid 3 worked with the WebKit team to repair the problem he also compromised the entire test as he gave the webkit team an unfair advantage against every other team as they did not have the knowledge of how this made (even with source code) and that the Webkit Team knew what everything that was being changed and the exact changes made compared to every other team. Webkit also had the advantage of starting work before every other team thus the entire test has been compromised. SandySoup (talk) 02:14, 24 April 2010 (UTC)
 * The Acid3 test itself specifies that the reference platform is a top-of-the-line Apple laptop. There is no bias. -- Schapel (talk) 11:45, 24 April 2010 (UTC)
 * Yes, but it does not specify the operating system. Also due to the fact that those are reference (as in hardware which is a maximum for a browser to pass for it to be valid) anything that is slower than the reference hardware can be considered valid as well. Another thing I noticed was that your position changed from any top of the line Mac to a laptop specifically. SandySoup (talk) 01:40, 26 April 2010 (UTC)
 * Well, I sincerely apologize if I misspoke once. How dare I do that! In any case, Opera doesn't come close to passing on an older laptop, and it doesn't pass on a newer laptop, so I'm not sure what your point is. In any case, what we need is a reliable source that states that Opera fully passes Acid3. As you are not presenting one, I see no case for stating that Opera passes Acid3. I'm still not seeing any bias. -- Schapel (talk) 02:48, 26 April 2010 (UTC)

←← Opera 10.50 for Mac is now a stable release. It's faster than Safari 5.0, which is faster than Safari 4.0 which passed the performance test, so I don't think it's reasonable to continue the exclusion of Opera at this stage. Thoughts? <sub style="font:bold 14px arial;color:#f27;">ɹəə pıɔnı  22:23, 19 June 2010 (UTC)
 * First, we cannot make an edit based on a conclusion -- that is original research. We need a source to cited instead. Second, when some tests say that Opera is faster than Safari, that doesn't mean it's uniformly faster at everything -- it is almost certainly faster at some things and slower at others. We cannot conclude whether Opera completes subtest 26 of Acid3 faster than Safari based on a completely different benchmark. In any case, when Opera does pass Acid3, Opera Software ASA will surely crow about it. -- Schapel (talk) 22:27, 19 June 2010 (UTC)
 * I vote for removing any references in regard to pass/not pass. This has become more a religious topic than a factual topic. A browser only passes if they claim they do, and as soon as they claim they do, there is a source to cite and that's taken as a fact? And only because a certain browser never claims a pass, they never do? That's all ridiculous.--DeTru711 (talk) 01:02, 16 June 2011 (UTC)
 * Whether a browser passes or not is fact. Whether we can say so in Wikipedia depends on whether there's a reliable source to cite. Any reliable source will do. Those are Wikipedia's rules, and if you don't like them you can debate them in the appropriate places. As far as your implication that there's a discrepancy between what Wikipedia states about which browser pass Acid3 and which browsers actually do, I've never seen any evidence that there is any such discrepancy. Do you have evidence that a browser Wikipedia claims passes doesn't pass, or that a browser Wikipedia claims doesn't pass passes? -- Schapel (talk) 17:19, 16 June 2011 (UTC)


 * Schapel I take it this is "your" article as if not you seem to be ignoring significant sections of what's being said about. e.g ".. the reference hardware is not a 3 year old top-of-the-line Macbook, it's defined as "whatever the top-of-the-line Apple laptop is at the time the test is run" ".  Pass/Fail is therefore a moving target therefore although a fact at a specific moment it is only so for that moment in time, like a stopped watch being more accurate than a working one.  QED  In addition to this the self-certification that seems to be being admitted as validly satisfying Wiki guidelines seems to me to be as close as can be to OR.  The PASS/FAIL colours are misleading and add nothing of OBJECTIVE value to the article.  They merely represent a vested opinion as to a momentary condition that are factually unverifiable. LookingGlass (talk) 08:01, 18 August 2013 (UTC)
 * Do not be too hard on Schapel -- all that is being insisted on here is that wikipedia must have reliable sources. If we're just talking about *truth* then clearly Opera passes, firefox passes, IE passes... and the reason they are marked as 'not passing' is due to the bias of the Acid3 author.  (Must Be Tested On Mac ... sheesh!  No bias towards Safari there, sure....)   I have just made an edit which uses yellow-coloration for browsers which are known to have passed some of the Acid3 tests.  That is fair, and keeps wikipedia from looking biased.  A bunch of red, and then a few green blocks for Apple and Google, definitely makes wikipedia look biased.  If this approach is *still* rejected, then I will be splitting the table up into four columns, Acid1 Acid2 Acid3score Acid3other, and giving green blocks to all the browsers with 100/100 in column three.  Actually, that would prolly be a good approach, whether or not the 'partial' moniker is acceptable consensus.  Any other thoughts on how to further improve the NPOV of this comparison table?  74.192.84.101 (talk) 17:14, 3 October 2013 (UTC)

Acid3 tests given too much prominence
Since the Acid3 score is contentious, it will perhaps help if we were to also reference additional sources. This data is already in the article, but in a separate section. Suggest we combine the sections into a Feature Tests table, and move it below the Web Technology Support section -- surely whether a browser supports CSS is more crucial than whether it scores 100 on the Acid3 test. Alternatively, it might make sense to split out some of the columns in WebTech, and create a new table called AdvancedWebTech, with columns for html5, acid123, xslt, xforms, webforms2, and so on. 74.192.84.101 (talk) 17:52, 3 October 2013 (UTC)

Need to click on cited page to get cited content
For the HTML5 test, the results for the Maxthon browser does not appear unless you click a button on the page that is cited. The URL of the page does not change. Thus, it's impossible for a reader to verify the information unless they know just what to do to see the cited information. How should we handle this case? I think we still need a citation for Maxthon's score, because the cited page does not contain any information for Maxthon when the user views it. -- Schapel (talk) 17:28, 21 November 2013 (UTC)
 * Nonsense. All scores are written in html source and just hidden by CSS (disabling CSS can show whole scores including Maxthon's). If complicated method is required to show Maxthon's score (ex. more than 5 clicks, click very small link on the bottom of the page, need special plugins, etc.), it may be considered to add another reference, however, only 1 click outstanding button "All browsers" is needed in this case. It's a kind of WP:BEANS--106.171.0.167 (talk) 00:17, 22 November 2013 (UTC)
 * Wikipedia content is supposed to be verifiable by all readers. The method for seeing Maxthon's score was complicated enough that I was unable to verify it until I was told exactly what to do to see it. We obviously need more information than the original URL if the information is going to be verifiable. I think a note will suffice in Maxthon's case. Something like "Click the Other Browsers button to see Maxthon's score." -- Schapel (talk) 15:05, 22 November 2013 (UTC)
 * In regards to WP:BEANS, what is it that we would be telling readers not to do that we don't want them to do. That's what seems to be nonsense. I want to tell them what to do so they can verify the information in the article, exactly as we are supposed to do. -- Schapel (talk) 15:07, 22 November 2013 (UTC)

Why no mention of WebSurfer browser?
I'm guessing it was mainly Twenty-Something's who wrote this article? I remember in the early-to-mid 90's seeing ad banners that said, "WebSurfer 5.0 The BEST browser". I laughed every time I saw it and said, "yeah right". I never clicked on it, never downloaded it. I already had Netscape Navigator 3.0, which was The King back then. But this WebSurfer browser should be mentioned here. It was indeed one of the also-rans who fought to get noticed in the shadow of Netscape Navigator. Anyone else remember this? You can still see the ads in The Internet Wayback Machine web site. I was in my early twenties back then and was a Netscape Navigator Fanboy, but today's Firefox Fanboys put me to shame, with their insanely blind romantic love for a piece of software. I'm waiting for California to legalize Fanboy-Firefox marriages, that's how out of control it has gotten. Anyway...WebSurfer 5.0...the best damn browser on the planet. Dropmeoff (talk) 03:15, 17 August 2009 (UTC)

Other missing browsers
There are a number of other browsers missing, it's as if RISC OS never existed. I don't have all the dates so I can't add this stuff myself... however you ought to be able to find information on: ArcWeb (Stuart Brodie, 1996), Webite (Doggysoft, 1995), Webster (Andrew Pullan - written in BASIC!, 1996), Fresco (ANT, 1994), Browse (Acorn, 1996?), Fresco/Voyager (modified version for ArgoNet), Oregano (Oregan Networks, 2000), Oregano 2, NetSurf (yes, it started on RISC OS), Bon Echo (port, Peter Naulls I think), plus the expected port of Lynx. Some of this stuff is available at ftp://ftp.demon.co.uk/pub/archimedes/www/ Fresco has its own Wiki page as it was deployed in a number of ARM-based (RISC OS internal) STBs. I believe that Browse was one of the first browsers to fully support PNGs. It is written up well at http://www.vias.org/pngguide/chapter02_02_05.html and as an update, full sources to Browse are available as a part of RISC OS Open. HeyRick1973 (talk) 19:52, 9 January 2010 (UTC)
 * Additionally Epiphany is not included here. --Khatores (talk) 18:23, 18 July 2011 (UTC)

Lolifox is also not listed here, it was a Firefox spinoff tailored for Anime/Manga fans. The domain http://start.lolifox.com is dead now. But a good reference write up located here: http://otakunoregion.wordpress.com/2010/02/24/have-you-heared-about-lolifox-or-maybe-you-already-have-used-it/ Izzzy12k (talk) 17:20, 15 December 2012 (UTC) Srware Iron (base on Chrome) has been omitted. — Preceding unsigned comment added by 95.144.98.229 (talk) 09:14, 4 January 2013 (UTC)

Also missing QtWeb. http://qtweb.net SDLarsen (talk) 04:25, 1 November 2013 (UTC)


 * There's no topic, no evidence of notability. As it is, making a comparison on this page for the "notable" browsers would make it several times longer than it is at present. TEDickey (talk) 09:11, 1 November 2013 (UTC)

I would like to see how Comodo IceDragon, Cyberfox and Waterfox stack up. I realize this page is already long and cumbersome, but the later two target 64-bit machines. Akinsm (talk) 23:01, 6 May 2014 (UTC)

Updating tables
I noticed it says that Chromium doesn't support PDF. Apparently it now does. APNG is now supported by Safari/Webkit. I think instead of saying "partial" for SVG it might be better to say what version it supports. Today SVG support is pretty good from all major browsers. And it would be good to check other things as well... — Preceding unsigned comment added by 86.195.237.34 (talk) 16:41, 7 October 2014 (UTC)

Modern Browser Only Condensed view option
Many people coming to the page are only interested in comparing current browsers to decide which to use. However, because all of the comparison tables are multiple screens long and compare every browser that has existed, they find the page to be mostly useless. We need a way to show only current information for those who want it, in order to increase utility. A method for allowing the viewer to sort information and suppress what they don't need would also be good.

This is a general comment applicable to all comparison articles. —Preceding unsigned comment added by 136.142.206.28 (talk) 22:35, 15 October 2010 (UTC)


 * I think the page is just way too long, with lots of original research. We should weed out the browsers that have never had a significant fraction of usage share and even pare down the number of columns in some of the table. Then we can work on citations for the data that is left. -- Schapel (talk) 00:26, 16 October 2010 (UTC)


 * There's a fine line between original research and common knowledge. This constitutes common knowledge since anyone can acquire the information with minimal efforts. However, collecting the amount of information shown here would be impossible without a team of people working on it. Wikipedia is the perfect community to maintain this page, and it is extremely useful, functioning qutie similarly to Consumer Reports (without the opinions). Bob the Wikipedian (talk • contribs) 04:16, 16 October 2010 (UTC)
 * As I said above: Let us create a userfied version of this page and start working on adding references for all cells! <b style="font-family:Courier New; display:inline; border:#009 1px dashed; padding:1px 6px 2px 7px; white-space:nowrap; color:#000000; font-size:smaller;">mabdul</b> 16:34, 21 October 2010 (UTC)

How about putting scores on every chart, then the last chart tells the score on every chart. :) Coleet (talk) 11:52, 21 October 2010 (UTC)
 * really: I can't imagine that this feature helps? Is the reader then smarter? <b style="font-family:Courier New; display:inline; border:#009 1px dashed; padding:1px 6px 2px 7px; white-space:nowrap; color:#000000; font-size:smaller;">mabdul</b> 16:34, 21 October 2010 (UTC)

In general I would WP should not drop old software from lists. Web browsers are a special case in how fast they get outdated (for security reasons - and for web standards..) and people shouldn't really be too concerned with the older ones to consider choosing them.. I think we should at least split the list (conservatively by say one year). I would want abandoned browsers one one side, and as that is not always known, the one year heuristic would help and be a clear line. All browser with non-trivial market share should be on the other side.. Possibly some browsers for non-mainstream platforms could get an exception/al treatment (if they are not know to be abandoned? might be the only browser?)? I can think of RISC OS and the Amiga that have some browsers made for them and at least RISC OS never had Firefox, Chrome etc. Ordering be version if not really helpful even if it would work, but could be if it actually ordered by date..

There is a small issue of historically important browsers, we all know what they are.. but still kind of WP:OR but probably not an issue as I'm not sure we need to group them and at least they would be easier to find in the smaller old list. comp.arch (talk) 18:28, 21 April 2015 (UTC)

Memory footprint comparison?
Shift-etc in Chrome shows page's memory footprint and isn't quite what I expected... — Preceding unsigned comment added by 85.156.167.10 (talk) 13:34, 24 January 2013 (UTC)
 * How much memory does each one use? Are there Windows-compatible browsers that use very little memory? E.g., maybe Lynx or Links? A column with memory usage comparison would be nice. Benefac (talk) 02:05, 6 November 2014 (UTC)

https://en.wikipedia.org/wiki/Comparison_of_web_browsers page takes 76 MB of memory on Chrome and I'd vote for footprint comparison... (109.240.255.248 (talk) 04:57, 20 January 2016 (UTC))

The article doesn't display properly.
I'm currently using Firefox with increased font sizes. The tables stretch off the edge of the screen. I've tried using reader view. The article doesn't show. 108.45.79.25 (talk) 21:39, 21 January 2016 (UTC)

Acid Tests? Why?
What is the point of the Acid tests? To determine whether the browser can enable every misfeature out there? Is there another test to see if the browser allows users to disable the misfeatures? 108.45.79.25 (talk) 21:57, 21 January 2016 (UTC)

Accessibility Question...?
I'm not seeing anything about this in the accessibility features. Which ones are free from flashing and have tools to block animation, zooming, etc.? Are any free from flashing? Which ones are accessible for people with photosensitive epilepsy? migraines? sensory processing disorder? Are any? 108.45.79.25 (talk) 18:54, 21 January 2016 (UTC)
 * Some of the other setions list which standards, scripts, and formats the browsers support, but not which ones they allow users to block. Some of these formats, such as animated gifs, can be extremely painful, can trigger migraines, and/or can trigger seizures. The ability to block these can be an important accessibility feature. 108.45.79.25 (talk) 22:03, 21 January 2016 (UTC)

Update to add Microsoft Edge
As I’m a member of the Edge team, I can not edit this page myself due to COI, but I’d like to request the following changes to update this page to the current situation.

Operating Systems Support
Add new row in table for Edge i:

Source: http://www.microsoft.com/en-us/windows/microsoft-edge

Browser features
Update Microsoft Edge row:

For auto-update it is the same deal as IE, so the note there should perhaps be made more generalised to reference both. Main difference is that there is no opt-out in Edge like there is in the IE about dialog.

Accessibility features
Add a row for Edge:

ACID Scores
Add Yes to Acid 1 column.

HTML5 support
Update to

Source: http://html5test.com/s/9abc972b83228a4f.html

Web technology support
Add Edge to table:

VML was dropped from Edge: https://blogs.windows.com/msedgedev/2015/05/06/a-break-from-the-past-part-2-saying-goodbye-to-activex-vbscript-attachevent/ Web Forms 2: this is no longer relevant as WF2 became HTML5 (along with Web Apps 1.0) over 10 years ago, but Edge does support large parts of what was WF2, such as the various date controls (the HTML5test link above shows this). Chrome should also be set to yes, as we both support at least as much of that spec as Firefox, which is listed as Yes.

In general, it is beyond the scope of this edit request, but this table could be updated with more relevant standards to today's web, such as HTML5, WebGL, Canvas, etc, rather than things like Web Forms 2, VML; frames, and CSS projection (both the latter which are  deprecated: http://www.w3.org/TR/html5/obsolete.html#non-conforming-features and  http://www.w3.org/TR/mediaqueries-4/#media-types

Plugins and syndicated content support
Edge needs to be added to this list with No's across the board.

Gears should be listed as No in Chrome as they dropped NPAPI and Gears in general was deprecated 4 years ago, so it probably isn't supported in any other modern browser either.

JavaScript support
Edge needs added here with Yes across the board, except partial for DOM3.

This could also do with including some more modern standards like ES5, ES6 (ES2015), ES7 (ES2016) etc., but this is also beyond this request.

Protocol support
Needs Edge added:

Image format support
Needs Edge added:

Internationalisation
Windows 10 (which Edge is part of supports the following languages by default:

Arabic (Saudi Arabia), Bulgarian (Bulgaria), Chinese (Simplified, China), Chinese (Hong Kong), Chinese (Traditional, Taiwan), Croatian (Croatia), Czech (Czech Republic), Danish (Denmark), Dutch (Netherlands), English (United Kingdom), English (United States), Estonian (Estonia), Finnish (Finland), French (France), French (Canada), German (Germany), Greek (Greece), Hebrew (Israel), Hungarian (Hungary), Italian (Italy), Japanese (Japan), Korean (Korea), Latvian (Latvia), Lithuanian (Lithuania), Norwegian, Bokmål (Norway), Polish (Poland), Portuguese (Brazil), Portuguese (Portugal), Romanian (Romania), Russian (Russia), Serbian (Latin, Serbia), Slovak (Slovakia), Slovenian (Slovenia), Spanish (Spain, International Sort), Spanish (Mexico), Swedish (Sweden), Thai (Thailand), Turkish (Turkey), Ukrainian (Ukraine)

https://www.microsoft.com/en-US/windows/windows-10-specifications#langs

Other languages are available as language packs (to keep the default size lower): http://windows.microsoft.com/en-US/windows/language-packs#lptabs=win10


 * Completed as far as I can see, please let us know if anything has been missed Aloneinthewild (talk) 12:29, 26 March 2016 (UTC)

Google Chrome support for Windows
Because of the undoing (5 April 2016) & redoing (6 April 2016) of the 4 April 2016 change to the Operating system support table, I hope to help resolve this dispute, in case it isn't over, & to prevent it from continuing. Since Google Chrome no longer supports Windows XP (Source: http://en.wikipedia.org/wiki/Google_Chrome: Platforms: Windows: Windows XP: http://chrome.blogspot.com/2015/11/updates-to-chrome-platform-support.html), Win. XP shouldn't be in the table for Chrome. However, this lack of support only means that Google will no longer create updates and security fixes for Chrome on Win. XP, it doesn't mean that Chrome doesn't still work on Win. XP (Source: above blog & http://www.google.com/chrome/browser/desktop/index.html). 104.178.189.70 (talk) 20:53, 9 April 2016 (UTC)

Same goes for Win Vista, which started April 1. 67.66.94.121 (talk) 07:26, 14 April 2016 (UTC)

Iridium Browser
I don't see any mention of it. It is another Chromium based browser, found here: https://iridiumbrowser.de/, is there any particular reason it has not been included? — Preceding unsigned comment added by 217.169.14.28 (talk) 12:11, 16 April 2016 (UTC)

HTML5 support
on 28 April 2016 I ran HTML5test over my browser, K-Meleon 75.0, which scored 406/555.

Unfortunately, due to the impoverished browser detection used by the author of HTML5test, it is almost impossible to reliably attach K-Meleon 75.0 to the score.

As a result, one editor insists on erasing my entry. That I have no problem with. However, given the inadequacy of the HTML5test suite, and the ease with which browsers may be spoofed by using the UA string, I suggest the deletion of the HTML5test table until a reliable browser detection method is employed by the author.

The simple fact is that due to the ease of browser spoofing, none of the entries in the table or the HTML5test pages can be considered authentic. 124.171.245.136 (talk) 09:12, 29 April 2016 (UTC)

Discontinued? browsers
On 3 Dec. 2015, Tim@ marked 6 browsers, discontinued. The article pages of 4 of them, ELinks, OmniWeb, Uzbl, & w3m don’t mention being discontinued or anything similar. Is he wrong about those browsers or has no one gotten around to updating those article pages?


 * Good catch. Uzbl must have been an accident as it's still being actively developed. I think the authors of ELinks and w3m probably regard their browsers as "finished" not "discontinued" as they are minimalist. From the author of w3m:

As w3m's virtues are its small size and rendering speed, adding more features might lose these advantages.


 * And as Wiktionary defines the word as "no longer available", OmniWeb can't really be considered to be discontinued either as they have a big download link on their website. And they made a preview release 7 months ago, so who knows maybe they're still actively working on it. --holizz (talk) 03:34, 3 April 2016 (UTC)

Uzbl needs updating of its Latest release version. Ver. 0.9 was released Feb. 28. 104.178.189.70 (talk) 06:39, 1 May 2016 (UTC)

Finishing incomplete edits
On 21 July 2016‎, Jasonanaggie unlinked Polarity only in the General information table, not in other tables. Since an article for Polarity, the browser, doesn't exist, should Polarity be unlinked in the other tables or should the "Wikipedia: Write the article first" guideline be followed strictly & Polarity be deleted from the article? The guideline does have exceptions. Safe Browser Secure is in 4 tables, not the 1st, General information. Since an article for that browser doesn't exist, should it be deleted from the article per above reason? Did someone remove it from the 1st table & not from the whole article? Most change descriptions are too short. There is room for a few more words. 104.178.189.70 (talk) 04:20, 14 August 2016 (UTC)

Tables too big for mobile
It seems the tables on this page due to the use of fix widths will overflow the amount of space available on the screen (see https://phabricator.wikimedia.org/T137892). Are there ways we could restrict the size of these tables or wrap them in a scrollable container? Jdlrobson (talk) 00:33, 29 November 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 3 external links on Comparison of web browsers. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20140725092954/https://addons.opera.com/en/extensions/details/autocomplete/ to https://addons.opera.com/en/extensions/details/autocomplete/
 * Corrected formatting/usage for http://www.schrode.net/opera/url_filtering/
 * Corrected formatting/usage for http://msdn.microsoft.com/en-us/library/cc304082%28VS.85%29.aspx
 * Added tag to http://www.maths-informatique-jeux.com/international/javascript_in_amaya/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 18:02, 11 August 2017 (UTC)

Putting Chrome next to Chromium
Now Chrome and Chromium are not close to each other, even if they are practically the same browser, because Chrome has Google Chrome in its name and Chromium does not. Anyone against renaming Google Chrome to Chrome so Chromium and Chrome are close to each other? — Preceding unsigned comment added by 83.33.11.160 (talk) 17:24, 16 September 2017 (UTC)

(West) Frisian
Mozilla website uses the word Frysk, which can be translated as West Frisian. Hence I suggest a replacement of the word Frisian with West Frisian. ––Sarcelles (talk) 09:36, 19 September 2017 (UTC)

GeckoFX
I missing GeckoFX in the Article. If Chromium is listed extra, also GeckoFX should be listed. — Preceding unsigned comment added by 94.217.49.221 (talk) 22:15, 5 November 2017 (UTC)

split continued and discontinued browsers
comparing discontinued or completely ancient web browsers with the current browsers of today is not all that helpful.

is there anyway we can agree to split out the browsers who have had a release in the last 1-2 years from all the rest of the totally dead browsers from 15 years ago ? thanks --Compn (talk) 22:20, 20 September 2017 (UTC)

I think it should have a separate category, especially if a browser is confirmed to be discontinued. It's nice to document whether they had support, but it's more interesting to see how much support a certain feature has in modern browsers. Benimation (talk) 00:12, 22 November 2017 (UTC)

Firefox's Auto-play blocking
Firefox does natively support Auto-play blocking for both plugin-based (Flash, Silverlight, etc.) and native HTML5 media. I am using it now!

This feature is lacked by, e.g., Google Chrome and is why I have recently switched. 174.55.24.54 (talk) 21:06, 5 March 2018 (UTC)

Safari for Windows missing
Since even IE for Mac is mentioned and all separate versions of Netscape, the Windows-version of the Apple Browser Safari should definitely be mentioned here. By the way: It's still possible to download it and run it on Windows 10! --91.64.224.116 (talk) 11:17, 14 March 2018 (UTC)

Edge/Safari - Included with Windows / macOS & iOS is not a valid "Price"
I feel as though Microsoft Edge and Safari should have the price indicated as "Free" rather than "Included with [respective operating systems]" While these are included with Windows and macOS/iOS, respsectively, they are also alternative (free) browsers compatible with multiple operating systems. This fits the same model as Konqueror. It does not have the price listed as "Included with KDE." Another possibility is suggesting that Chrome's Price: "Included with Chrome OS and Android". These are simply listed as having a price of "Free." Furthermore, this column is specifically referring to the actual price of the browsers, which in these cases is, in fact, free.Jtrnp (talk) 14:05, 27 March 2018 (UTC)

Order of table [for protocol support]
The table Comparison of web browsers is getting too wide, and HTTP/2 drops off. Arguably it's more important to know than HTTP support (or Gopher or IRC).

A column of (mostly) yeses seems useless [at least for HTTP]. Could I just drop it (or move last), that's the easier option. Mosiac is historically important, but need we maintain a column, where only it (or some other old/discontinued browser) differs?

Gopher is not really used anymore, I say we should just remove it. I don't really care if some browsers support" (I suspect it may be outdated "yes" in for some). It's just more work to move, but if you insist, I could. Unless anybody objects, I assume I have permission.

IRC is still useful, but people may just use desktop programs or website gateways (not built in feature, that is very rare). Drop or move to last ok? comp.arch (talk) 16:34, 1 April 2018 (UTC)

Privacy section Comment
@Gstree, @Realmdee, In the Privacy section, what did you mean by "Yes" and "No" under "Website Visitor Tracking"? Usually that term applies to cookies or fingerprinting managed by target websites. All browsers listed have an option to block cookies, but don't do so by default. Or did you mean the browser itself tracks the user, and reports back to the browser's parent company? I think most browsers have the right to report back to their parent company. These are different aspects of privacy and probably need two columns, with citations to sources. I'd like to expand the section to cover broader privacy policies of these browsers, and maybe other terms of use. Numbersinstitute (talk) 17:29, 8 December 2018 (UTC)

No Tor Browser?
I was surprised to not see one of the most known web browsers for privacy protection the "Tor Browser" https://www.torproject.org/ May I know why? Or maybe you are not aware of it (which will surprise me) Do you want me to care about it and add it? Nudibranch (talk) 14:37, 7 May 2019 (UTC)
 * If you have properly sourced content then go ahead and add it. Captainllama (talk) 11:00, 20 June 2019 (UTC)

Image Format Support notes for Midori
Midori once had its own notes for JPEG 2000 (12. Supports JPEG2000 through QuickTime plug-in.) & SVG (13. Not able to render SVG documents fully [22].). Now it shares notes 13 & 14 for those categories w/ Safari. Notes 13 & 14 only mention Safari, not Midori. Seems like an error.--99.7.207.171 (talk) 06:20, 22 December 2019 (UTC)

Brave browser
Brave browser is the new Brave browser started by Brendan Eich, who invented JavaScript and co-founded Mozilla, after resigning as Mozilla's chief executive is now heading a new startup called Brave Software that promises to make the Internet safer and faster when the company publicly launches it in early 2016.

See: http://www.cnet.com/news/mystery-startup-from-ex-mozilla-ceo-aims-to-go-where-tech-titans-wont/, Also check: http://softwarerecs.stackexchange.com/a/31902/3474

Homepage: http://www.brave.com, Github: https://github.com/brave/browser-laptop

Note: This browser should be added into Web technology support section.


 * Latest release version should be added from its article, 0.23.19 (June 28, 2018), as of July 21, 2018.104.178.189.70 (talk) 00:46, 22 July 2018 (UTC)


 * Ditto, but "Android: 1.4.3 & Desktop: 1.0, 13 November 2019", per its article.--99.7.207.171 (talk) 07:15, 22 December 2019 (UTC)

Microsoft edge misleading licence
Microsoft Edge is stated as being licensed under BSD, which is not true. Only the core rendering engine, chromium, is BSD licensed, so I think it's misleading. I'll remove The explanation and leave the note about rendering engine license. Šijanec (talk) 21:01, 22 March 2021 (UTC)

Browser manufacturer in browser name inconsistency
Why do some browser names include the manufacturer & others don't? This article has a problem of not being consistent. Some browsers have it, some don't, & both cases aren't consistent. When inconsistent, browsers appear in different rows in 1 table relative to other tables. Two examples are Google Chrome & Microsoft Edge. 2600:1702:3790:1520:C0BD:CCC6:570A:6BE1 (talk) 21:39, 16 February 2021 (UTC)

Someone has tidied up the Edge/Microsoft Edge inconsistency, now called Microsoft Edge. Chrome is still called Google Chrome in some places (fewer places), I believe it should be Chrome because it is very well known as Chrome, also it makes sense for Chrome to be alongside Chromium in these lists. I think Mozilla Firefox should be just Firefox.--12think (talk) 07:47, 15 July 2021 (UTC)

Errata
ReveurGAM (talk) 07:00, 22 September 2021 (UTC)
 * The following browsers are missing from this article: Puffin, Tenta, Epic, Iridium, LibreWolf, Ghostery Privacy, DuckDuckGo, Ungoogled Chromium, Bromite (Android), and FreeNet.
 * Others, like Waterfox and SRWare Iron Browsers, are not listed in most tables.
 * Privacy & Security section is needed.
 * Coloration of Acid Tests section is inconsistent.


 * DuckDuckGo is not a web browser. It is a search engine. --2600:1702:3790:1520:CD9C:7274:A73D:A5C2 (talk) 04:05, 13 June 2022 (UTC)

HTML5 support section
I'd like to question the relevancy of the scores from html5test.com. The version numbers on the page don't even match up with the current version of the browsers. It's like nobody updated the page in years. It says (https://html5test.com/results/desktop.html) the current version of Chrome is 66 and 17 for Edge. However it's 104. For Edge too since they switched to Blink. The timeline shows, it hasn't been updated since 2018. imao the entire section is advertisment for an unmaintained opinionated page that just gives you a hardcoded score based on your user agent and we should remove the section because it only consists of that page. The article about HTML5test should be changed or removed too. 2A02:2454:91E7:5B00:C5C7:325C:7BFD:62F4 (talk) 00:09, 29 August 2022 (UTC)

Lynx and IDN
Lynx has supported IDN since 2009 TEDickey (talk) 01:11, 23 November 2022 (UTC)

Midori Engine Update
Midori's Engine should be updated to show the currently listed WebKit was used until 2019 or 2020 & Electron used afterwards. Edge & Firefox list 2 engines for 2 different periods. 2600:1702:3790:1520:3C02:35B0:6110:AC7D (talk) 05:41, 27 November 2022 (UTC)