Talk:Firefox/Archive 17

Infobox image
I see there's been an edit war over the lead image in Infobox web browser. I'd like there to be some sort of agreement or consensus on what gets represented in the lead image, so I'm starting a discussion on this topic here. I personally want to see Firefox represented at full functionality, to be as familiar to the personalised Firefox experiences as possible, rather than an "out-of-the-box" look that a majority of Firefox users won't find that familiar to how they use Firefox. I'd like there to be a window drop shadow effect as well to make it even more familiar to how Firefox would look running in the vast majority of operating systems such as Windows 10 and macOS. I'd also like the screenshot to be in English, since this is, after all, the English Wikipedia, en.wikipedia.org to be exact. As for what version should be represented, I really don't mind as long as it matches the look and feel of the current version. I concur with the sentiment that 57.0 doesn't look discernibly different to 61.0. For reference, here's the two screenshots I've uploaded for 57 and 61. – PhilipTerryGraham (talk ·&#32;articles ·&#32;reviews) 08:09, 21 July 2018 (UTC)
 * Incorrect. Software screenshots says the following

Wikipedia's Manual of Style for images reads that images displayed in the lead of an article should be "natural and appropriate visual representations of the topic; they not only should be illustrating the topic specifically, but should also be the type of image that is used for similar purposes in high-quality reference works, and therefore what our readers will expect to see." To reflect this guideline, the main screenshot should portray the software in its most common form by using its default settings.

While an "initial" state is desired (i.e. one with a blank document, or showing a "welcome" menu), it may also be desirable to load generic data or filler text into the depicted software (especially if it is graphics software or part of an office suite) in screenshots to show the software in "normal" use. It is preferable that the demonstration content itself is self-made, freely licensed or in the public domain to prevent the accidental inclusion of non-free content if it can be avoided. It has been a common practice for web browser screenshots to use images of Wikipedia's front page. There have been concerns over the practice by some, however, as it is a self-reference, and because Wikimedia Foundation logos were previously non-free (although this is no longer the case). Most major web browsers now have their own dedicated "start" pages built-in, which typically display recently visited or bookmarked sites, that can serve as an alternative.
 * This passage was written by me based on common consensus and practices. ViperSnake151   Talk  18:59, 21 July 2018 (UTC)
 * Don't see how I'm "incorrect" about an opinion, especially as I don't see how the WP:SCREENSHOT guidelines are being broken here. I'm advocating to "show the software in "normal" use", rather than the ""initial" state". The guideline appears to state that either one is okay, so this is even more so not tangible evidence to prove I'm "incorrect" about any of the things I'd like to see in the screenshot. It also doesn't say anything about which version of a screenshotted software should be displayed as a lead image, which is something I'd really appreciate an opinion on. – PhilipTerryGraham (talk &middot;&#32;articles &middot;&#32;reviews) 14:37, 22 July 2018 (UTC)
 * The problem with normal use is that we have to more vigilant for copyright violations. The start state appears to be immune from this. However, a multi-tab view where other tabs were only showing titles should not violate copyright. And Wikipedia's front page should also avoid the problem, but the editor taking that screen shot should be careful to avoid any copyrighted content on that page. Walter Görlitz (talk) 17:16, 25 July 2018 (UTC)
 * Yeah, and that's exactly the reason why the tabs and bookmarks have been decked out with various Wikimedia projects in lieu of other copyrighted websites, if you haven't noticed. – PhilipTerryGraham (talk &middot;&#32;articles &middot;&#32;reviews) 04:23, 10 August 2018 (UTC)
 * For variety, US government sites are typically in the public domain. Other sites that are public domain, CC-BY or CC-BY-SA would be fine as well. Have fun with the tabs! --LABcrabs (talk) 17:38, 10 August 2018 (UTC)

Criticism
For several years now, Firefox users have criticised the developers for removing features and diminishing the customizibility of Firefox. It seems that they are trying to mimick the Chrome interface, leading to the response that people preferring Chrome, would use that program. Because this criticism is a theme recurring on many discussion pages all over the web for many years, I think it should be mentioned in the article. Also I don't understand this removal of useful information added by another user. Bever (talk) 11:16, 4 January 2019 (UTC)
 * WP:INDISCRIMINATE. If you can find a reliable source that discusses these things, such as from Wired, or a computing magazine, it might be worth discussing. We don't post news about every product. Walter Görlitz (talk) 15:29, 4 January 2019 (UTC)

Firefox version history merge
Pursuant to the deletion discussion at Articles for deletion/Firefox version history, I have merged Firefox version history into that section of this article. Since this substantially increases the size of this page, editors here might want to think about breaking out other sections into freestanding articles. The merged-in content is also subject to reasonable pruning. Cheers! bd2412 T 02:33, 11 February 2019 (UTC)
 * This is completely untenable. The largest section has 406,000 bytes, which regards Firefox's version histories. The only section of the article that can be split out is what has been merged into it. We should probably move this somewhere off main before it can be reduced to an acceptable size, or RfC it for deletion. Onetwothreeip (talk) 08:15, 11 February 2019 (UTC)
 * I have reverted the merged content and it should not be in this article until such time as we know what to do with that content. There is no need for haste and the deletion discussion did not provide any detail on how a merge should be conducted. Onetwothreeip (talk) 00:47, 13 February 2019 (UTC)
 * I agree that this is not the best situation. Nevertheless, that was the outcome of the discussion. I will move the section to template space and transclude it for now, but a separate consensus must be developed to produce a different outcome. bd2412  T 13:23, 15 February 2019 (UTC)
 * Please see my comment at Talk:Firefox version history for my idea of what to do with this information. Seems to me, it belongs in the History of Firefox article (assuming we're keeping that one) rather than this one. - dcljr (talk) 02:04, 16 February 2019 (UTC)
 * I have no objection to that resolution to the problem. I would keep it as a template (now Template:Firefox version history), which frankly makes it easier to change the host page. Perhaps the template can be split into multiple smaller templates according to its current component subsections. bd2412  T 02:09, 16 February 2019 (UTC)
 * I'm not sure using multiple templates to transclude the tables into the "History…" article is actually a viable option. Using templates to store normal article content (which, I believe, these tables would qualify as) would seem to run afoul of WP:TG. - dcljr (talk) 02:33, 16 February 2019 (UTC)
 * I think we should just delete it entirely, until someone objects to removing it., I believe you restored it only because that was the conclusion of the AfD, not because you think it should be included. I have no problem with you merging it as a result of the AfD, but once it is content in another article than anybody can reasonably remove it per WP:BOLD and WP:BRD. It's just far too big a table to be useful, I don't believe anybody would read it from start to finish. Onetwothreeip (talk) 02:52, 16 February 2019 (UTC)
 * My issue with that is that there was a discussion on the previous article, and a clear absence of consensus in that discussion for the complete removal of this content from the encyclopedia. The discussion would have been closed as kept, but for all the SPA involvement on that side. I would suggest as an alternative going through the table and picking out significant developments, and retaining, say, the most pertinent 10-15%. bd2412  T 03:04, 16 February 2019 (UTC)
 * Sure, but it doesn't take a discussion or a consensus to remove content from Wikipedia. I don't know which developments are particularly important, but I don't think something as long as that should be on the article in the meanwhile. There doesn't seem to be anybody against removing that table from this article. The absence of a discussion to remove it from Wikipedia entirely is secondary. We have it saved on a template, alternatively I could keep it on my user page, but I don't see anybody who thinks it belongs in this article. Onetwothreeip (talk) 03:59, 16 February 2019 (UTC)
 * Strictly speaking, two of the !votes in the AfD were specifically to merge into this article. A third was to merge to the "history of..." article, and a fourth was to merge it between the two. From the standpoint of evaluating that discussion, I would have no objection to moving the content to the "history of..." article pending further discussion or refinement. bd2412  T 04:20, 16 February 2019 (UTC)
 * I would remove it from that article as well, if it was there. Again it's not so much that I think it should be removed from somewhere, it's that nobody thinks it should be retained there, at least enough to actually revert me removing it. Onetwothreeip (talk) 04:28, 16 February 2019 (UTC)
 * Come, now, . The discussion at Articles for deletion/Firefox version history clearly does not support the idea that "nobody thinks it should be retained" at History of Firefox, as bd2412 just explained (not to mention my own opinion, expressed above in this thread). - dcljr (talk) 09:25, 16 February 2019 (UTC)
 * at least enough to actually revert me removing it. Onetwothreeip (talk) 09:38, 16 February 2019 (UTC)
 * Yeah, I'm saying someone would revert you. - dcljr (talk) 09:41, 16 February 2019 (UTC)
 * Let's find out? Onetwothreeip (talk) 10:06, 16 February 2019 (UTC)
 * Let's not. - dcljr (talk) 10:44, 16 February 2019 (UTC)

More importantly, though, I think the process by which we got to this point has been fundamentally flawed. While I appreciate that this was a "complicated close", nevertheless, I believe it was done improperly. According to Guide to deletion, "A decision is either to 'keep' or 'delete' the article. Discussions which fail to reach rough consensus default to 'keep'. The decision may also include a strong recommendation for an additional action such as a 'merge' or 'redirect'." Based on the lack of consensus to merge it specifically to here (I agree with Onetwothreeip about this), and the admitted "absence of consensus […] for the complete removal" of the content (I agree with bd2412 about this), it seems to me that closing the discussion as "no consensus to delete, but possible emerging consensus to merge elsewhere, therefore a merge discussion should be undertaken on an appropriate talk page" would have been more appropriate — especially given that the discussion for deletion had already been relisted twice for further comments (because of a lack of consensus) while no proper merge discussion, including notification of the watchers of the potential target page(s), had taken place. I therefore ask bd2412 to reconsider his closure on this basis. I also object to the way the content was moved into the template. I don't think there's any accepted precedent for copy-and-pasting article content into a template simply to get it out of its own stand-alone article, whether with the intent to transclude it into another article (as I mentioned above) or to hold it while waiting for it to be properly merged into another article. Therefore, I (also) ask that Firefox version history be temporarily restored, the template be deleted, and a proper merge discussion take place at Talk:Firefox version history, with notifications given at both Firefox and History of Firefox. - dcljr (talk) 09:25, 16 February 2019 (UTC)
 * I agree completely, but reducing that article is as appropriate (if not more) than merging it. Onetwothreeip (talk) 10:06, 16 February 2019 (UTC)
 * I've decided to discuss it at Talk:History of Firefox instead, since that's actually where the content originated before being moved to this article (and where I hope it will end up). - dcljr (talk) 10:44, 16 February 2019 (UTC)
 * In practice it is not the case that the result of AfD discussions must always be a binary keep/delete. Merge/redirect outcomes are an occasional result, and are carried out as such. In some cases, the closing admin will leave it to the disputants to carry out the merge, while in others the closing admin will carry out the merge directly. I like to do it myself because otherwise an article with consensus for that outcome can linger for months while the details of the merge are worked out. However, the discussion here is persuasive, so I have restored Firefox version history pending the outcome of such discussion. I will remove the templated version from this article and delete the template. bd2412  T 13:52, 16 February 2019 (UTC)
 * Thanks. I should clarify that I didn't mean to imply that deletion discussions must end in a simple Keep or Delete, only that a Merge conclusion should only follow a consensus to merge content to a particular place, which I don't believe was achieved in this case. Anyway, we'll see what happens with the merge discussion... - dcljr (talk) 22:57, 16 February 2019 (UTC)

Light Web Browser - Should It Be Merged To This Wiki Page?
The title says it all; you can also discuss merging here: https://en.wikipedia.org/wiki/Talk:Light_(web_browser) --NinLEGWho 23:42, 27 March 2019 (UTC) — Preceding unsigned comment added by VarhOuh (talk • contribs)

x64
You have twice claimed that there is a preference of the term "x64" over "x86-64" in the English Wikipedia, despite evidence to the contrary. So, where is the evidence for your position? Where has this been "discussed in previous talk page discussions"? A search of the archives of this talk page (Talk:Firefox/*) for the terms "x64" and "x86-64" did not turn up anything relevant. If you're alluding to other talk pages, please specify which. - dcljr (talk) 04:23, 3 May 2019 (UTC)
 * The fact that it's here and has been reverted back by other editors over time is the evidence.
 * There's no need to ping me as this article is on my talk page. Walter Görlitz (talk) 05:00, 3 May 2019 (UTC)
 * If those users are applying an actual Wikipedia convention, then it is most likely that of maintaining the status quo when optional styles are available, neither of which is preferred (as I explained to you on your talk page). It is not evidence of a Wikipedia-wide preference for one term over the other. For the benefit of other readers, I (again, as I did on your talk page) point to Manual of Style/Computing, where an explicit statement exists indicating that "x64" is not preferred over "x86-64". Unless that part of the guideline was put there in contravention of consensus (if so, it wouldn't be the first time), I think we need to act as if there is no general preference for one term over the other. Now, because the convention exists in this particular article to use "x64", that should indeed be maintained in the absence of a compelling reason to change it, in accordance with MOS:STYLEVAR. But if you try to extend that perceived "preference" to another article, it may not be valid there. This all started because your revert was justified with the phrase, "Not the usual notation on Wikipedia". That was not the proper justification for the revert, and it should not be used in the future to justify similar reverts here or in other articles. That's all I wanted you to understand. - dcljr (talk) 03:50, 5 May 2019 (UTC)

Outdated
Gecko is no longer used as the rendering engine. FF Quantum is the current stable version, not a future project. Need newer user stats than 2014. And so on. — kashmīrī  TALK  00:30, 27 June 2019 (UTC)
 * Gecko is still used as the rendering engine, Quantum is just a shiny new umbrella name of some improvements. Rctgamer3 (talk) 04:35, 27 June 2019 (UTC)

Observation: The “about:blank” glitch.
I have noticed that when a JavaScript bookmarklet tries to open a website in a new page, the URL bar only shows the URL after the loading of the page has finished. Prior to that, it only shows “about:blank”, which is not the actual URL of the page that is being loaded. Maybe this information is useful to some editors. And who else has observed it? --Handroid7 (talk) 03:48, 15 September 2019 (UTC)

"Fox of Fire" listed at Redirects for discussion
An editor has asked for a discussion to address the redirect Fox of Fire. Please participate in the redirect discussion if you wish to do so. -  C HAMPION  (talk) (contributions) (logs) 09:54, 2 October 2019 (UTC)

"MFx" listed at Redirects for discussion
An editor has asked for a discussion to address the redirect MFx. Please participate in the redirect discussion if you wish to do so. -  C HAMPION  (talk) (contributions) (logs) 09:55, 2 October 2019 (UTC)

Firefox browser and Firefox product family
Can this page be separated into two pages, one for the browser, and one for the product family? SportsFan007 (talk) 08:15, 22 October 2019 (UTC)
 * I'm going to personally lean towards no. While I did notice the new Firefox 70 icon, the Firefox.com site still prominently shows the web browser, and the other Firefox software (Lockwise password manager, Monitor privacy check, Send temporary file upload and Pocket bookmark service) are all complimentary aka. add-ons or web services, although some have dedicated apps and/or support non-Firefox browsers. All this to say, the Firefox name generally refers to the browser. For other uses, a disambiguation page is more than enough. --LABcrabs (talk) 22:20, 22 October 2019 (UTC)

Fx shifted from 6 to 4 weeks between versions
I guess the part concerning updates needs updating. Alfa-ketosav (talk) 10:17, 26 April 2020 (UTC)

Is Firefox "free"?
The top part of the article says Firefox is a "free and open-source" web browser, however I was under the impression that parts of Firefox were non-free (free-as-in-freedom). Is this accurate? --Sebastian Hudak (talk) 17:22, 22 June 2019 (UTC)
 * It is released without cost to the person who installs and uses it, so it is free. Walter Görlitz (talk) 18:30, 22 June 2019 (UTC)
 * "Free" when used as "Free and open-source" doesn't refer to cost, it refers to "freedom", mainly the program's license and the rights it gives to the users. I was under the impression that parts of Firefox were "non-free". Cost is irrelevant to "freedom". Sorry for the confusion. --Sebastian Hudak (talk) 21:30, 24 June 2019 (UTC)
 * That's one interpretation of what free and open-source software means. There are four freedoms and none of those appear to be contravened by Firefox. Which are you concerned with? Which do you have sources to support that contravention? Walter Görlitz (talk) 21:35, 24 June 2019 (UTC)
 * The Firefox branding (e.g. logo) is non-free. Everyone may compile a completely free version of Firefox, but without using its branding. This was once an issue for Debian and Ubuntu. See Iceweasel. Tgeorgescu (talk) 01:40, 25 June 2019 (UTC)

I work for Mozilla so changing this very important page might be a CoI. Mozilla announced a change in the Firefox brand (https://blog.mozilla.org/opendesign/firefox-the-evolution-of-a-brand/) where Firefox will be the masterbrand and the spezific products have specific names. Firefox therefor does not reference anymore just the browser but more products so this page should imo move to Firefox_browser and Firefox should be an overview of all products of the umbrella brand. Rraue (talk) 09:49, 1 July 2019 (UTC)


 * Thank you for disclosing your conflict of interest. Per WP:Official names, until Firefox browswer catches on as the common use of the name, the article's title should remain as is. Also, please sign your edits by inserting 4 of these: ~ before publishing your edit. Thank you!  Orville1974 talk 13:55, 26 June 2019 (UTC)

A majority of modern day browsers are free and make money of ads, or in Firefox's case donations/royalties. Drakesdrs1 (talk) 15:24, 20 June 2020 (UTC)

Should we specify that OS X 10.9-10.11 is supported with ESR releases?
In the infobox and system requirements table, I've noted that OS X 10.9-10.11 are supported by the ESR channel, but 10.12 is needed for the standard release. However, this goes against the precedent of the last time this happened, when OS X 10.6-10.8 were dropped in 2016. Should I leave it the way I edited it until 2021, or just immediately bump the requirements to macOS 10.12?Herbfur (talk) 15:35, 28 July 2020 (UTC)

File:Firefox Logo, 2019.png and others
Mozilla is undergoing a transition to these logos, it seems. Maybe someone can put something in about that? — Preceding unsigned comment added by Seemplez (talk • contribs) 11:09, 24 June 2020 (UTC)
 * This logo is for the Firefox brand (which now encompasses multiple properties). Firefox Browser (née Mozilla Firefox) still uses the existing logo but with an art style patterned upon it. ViperSnake151   Talk  23:55, 20 September 2020 (UTC)

Logo Controversy
Due to the high amount of memes of the Firefox logo being oversimplified, and a bunch of media coverage on it, should we start adding a controversy section regarding the logo? — Preceding unsigned comment added by The great Jay (talk • contribs) 04:06, 8 March 2021 (UTC)
 * I don't see why this should be classified as a controversy. Some very vocal handful of individuals have been mass-spreading nonsense posts (FUD) about the logo on social media and sites such as Reddit, nothing more. Rctgamer3 (talk) 18:14, 8 March 2021 (UTC)
 * Seems like WP:NOTNEWS to me. IT does not seem that the "new logo" is actually used anywhere. Walter Görlitz (talk) 22:32, 8 March 2021 (UTC)

More Updates
On a Motorola Moto G5 Plus (ARM Cortex-A53), which apparently won't get updates beyond Android 8.1.0, Firefox Beta reports it's on version 92.0.0-beta.8 Sorry, I can't begin to figure out how to update the chart. Thanks Nei1 (talk) 16:13, 4 September 2021 (UTC)

Title Change Request
"Firefox" is used for multiple things. So, I propose that the title of this article be changed to "Firefox Browser" to avoid confusion. Contributer1234 (talk) 15:05, 27 October 2021 (UTC)
 * I agree. This also matches Mozilla's branding guidelines which make a distinction between Firefox and Firefox Browser. – Anne drew  15:48, 27 October 2021 (UTC)
 * Oppose: "Firefox Browser" is not a common name; the proper full name would be "Mozilla Firefox". But everyone just calls it "Firefox". —Dexxor (talk) 05:43, 29 October 2021 (UTC)
 * I'd prefer "Mozilla Firefox", as that seems more conventional and is used in the window title. The "Firefox Browser" suggestion is reminiscent of "Focus car" rather than "Ford Focus", and seems unnecessary as it is a household name. Just my 2¢. Lapisgaming (talk) 09:24, 29 October 2021 (UTC)
 * Oppose. While it's true that multiple subjects are named Firefox, the most popular usage so far this millennium is for the Firefox browser. It is best to simply keep the title to Firefox, as that's the most common name, not Firefox Browser. Further, the domain Firefox.com points directly to the browser. On that website, the Firefox Browser text has Firefox in bold, highlighting the common name; "Firefox for Desktop" also appears. As for Mozilla Firefox, that was the common full name in the past, but its official use is reduced today. Other products (Firefox Monitor, Firefox Relay, Firefox Focus, etc.) and usage (novel, film, etc.) are less popular and less notable, so they can go on Wikipedia's disamb page. --LABcrabs (talk) 15:32, 29 October 2021 (UTC)

Info-Box Photo
The photo in info-box shows a screenshot of firefox at wikipedia website. It should be more informative and topic focused if we use the screenshot of firefox homepage instead. 2409:4050:E9C:BF88:0:0:4ACA:C014 (talk) 02:04, 16 November 2021 (UTC)