Mozilla Firefox

“ The early interactive mediaspace was a gift economy (see Barbrook2) . People developed and shared new technologies with no expectation of financial return. It was gratifying enough to see one's own email program or bulletin board software spread to thousands of other users. The technologies in use on the internet today, from browsers and POP email programs to streaming video, were all developed by this shareware community of software engineers. The University of Illinois at Champagne Urbana, where Mozilla, the precursor to Netscape, was first developed was a hotbed of new software development. ”

“ It was a Firefox Add-on named Wired-Marker which uses a .JSON database to store marked web text (or for that matter, any selected object on a web page) . Since I am running Windows 7, and Linux on my desktop, and occasionally an Old MacBook with identical browser setup, the developers of Wired-Marker suggested to install Dropbox and store the JSON database in the cloud and link it from Firefox, so all three OS's can have the same data. The slowdown was because Dropbox constantly synced the database and this in turn affected Wired-Marker and slowed down the browser. ”

“ Firefox 52.0.2 (32 bit) on Windows 7 is my main browser for Wikisource. However, the problems in the weekend were happening in IE8 (Windows) and whatever the latest version of Safari is on the iMac as well. Note that it was specific to the Page: namespace. While I occasionally have slow page loading that's normal in a household with an inveterate internet video watcher. They go to bed and my connection speeds up. Beeswaxcandle (talk) 07:36, 5 May 2017 (UTC) Thanks for the reply. Essentially we have the identical setup, both OS and software. ”

“ Sorry for not clarifying "Show edit toolbar" is the legacy toolbar. I assume you are using Windows. The problem is with our Mediawiki software update of Tuesday. It was mucked up somehow. The Mediawiki programmers test the software on all browsers, and this problem may have to do with local modifications to our English Wikisource. The problem is that in other browsers and Firefox in Linux work fine, (see my comments above) . There is nothing we can do until someone in the know will look at it. ”

“ Currently, the tool doesn't appear in my sidebar either, and common.css has nothing to do with the sidebar tools. — Ineuw talk 16:16, 24 June 2016 (UTC) It would be important to all who experience problems to specify the OS and the browser + version. In my case all of these problems come from Firefox. I tried the same with Chrome and everything works. If anyone has problems, please list the OS and browser + version here, or create a new bug report if the problem is not the same as task T138554. This bug report was only in relation to page layout changes in Firefox 48.01b and 48.02b. ”

“ I should create a table for all the browsers in various OS's. I tested the OCR in the following browsers using Ineuw for the advanced toolbar and my public account configured for the legacy toolbar.
In both Windows and Apple - Logging out and then in works if not on the first try then the second. Advanced toolbar In Windows and Apple - It always works with the advanced toolbar in all browsers. This includes, Firefox, IE 11, Chrome, Opera and Safari. Legacy toolbar In Windows - It works in all browsers except in Opera, where logging out and in brought it up on the second try. ”

“ If you add the contents of User:Wolfman test account/monobook.js to your javascript, you should be able to welcome multiple people with a single click. A 'welcome everyone' tab will appear if you go to the newuser log. This is tested on FireFox, though it probably works on IE as well. If you try it, and it doesn't work, please let me know so I can improve it. It pops a second window, which will close automatically when the tagging is finished. I am working on making various other useful scripts publicly available as well. For example, I can post handle a copyvio posting with a single click. ”

“ O'Reilly says he wanted to direct media and community attention to the other deserving projects that had also encouraged Netscape to release Mozilla. "All these guys had so much in common, and I was surprised they didn't all know each other," says O'Reilly. "I also wanted to let the world know just how great an impact the free software culture had already made. People were missing out on a large part of the free software tradition." ”

“ But if things degrade gracefully enough, and I move that bar lower at a steady pace, then fine. Perchance the best move the wmf projects could make would be to have a nag-message at the top of every page directing those running IE6 to the Firefox download page; omit a [dismiss] link. Cheers, Jack Merridew 08:06, 19 August 2008 (UTC) (further) I just opened this page and the search page in IE6 and a) didn't get any js messages and b) something about User:Struthious Bandersnatch/template/comment is rendering poorly in IE6; it's all bold and rather run together. ”

“ You can read more about the server work. There will be more notifications and updates about this. In Firefox, the visual editor would sometimes just jump down to the bottom of the page when you double-clicked on a table cell. This has now been fixed. Changes this week
It will now be easier to list IP addresses that don't have to solve CAPTCHAs. You will now be able to mark Echo notifications as unread. The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 March. It will be on non-Wikipedia wikis and some Wikipedias from 22 March. ”

“ Ajax sysop (new version of obsolete script) Hello Jayvdb. You were using "Getmoredata.js", which adds a list of subpages (and a block log for user pages) on the deletion form. That script has been replaced by the better-written and more extensible Ajax sysop. I switched you to the new script (see a screenshot comparing outputs) ; if you prefer to use the old script, I'll add the source code directly to your script file since it will no longer be maintained.
You'll need to refresh your browser (CTRL+R in Firefox) to see the new version. ”

“ On some devices, fonts may not render correctly, or font sizes may be mismatched. When using the Firefox browser, you can adjust the default font settings per script. To do so, open the “Settings” page; select the “General” tab; in the “Fonts and Colors” section, click the “Advanced” button, and adjust the settings as desired.
Some ad-blocking software may hide all or parts of the advertisements reproduced here from the original book. To see them, disable your ad-blocker (no new ads are included in Project Gutenberg ebooks) . ”

“ Page: is then ultimately there to verify nobody changed anything content wise and not for it's prettyness or exactness. I changed the line-height from 1.4 to 1.0 em anyway. -- George Orwell III (talk) 07:22, 27 August 2013 (UTC)
Your point is well taken and thanks for your time. Yes, the results are different in the main namespace. Just FYI, there is no discernible difference between Safari and Firefox rendering. — Ineuw talk 18:24, 27 August 2013 (UTC) In a related question, how do I locate the the WS Common.CSS to view at the contents? Thanks. ”

“ My proposal is to change all these size templates to use a specific percentage rather than a relative term like "smaller" or "larger". From my testing, it appears that doing so will make the text size consistent for all browsers. This is how it is done at Wikipedia—the standard "small references" class in their MediaWiki:Commons.css is 90%, not "smaller".
I suggest reducing the amount of difference between the successive templates for our Firefox and IE-using readers. ”

“ I tried them both in my sandbox and still I cannot see any difference in comparison with plain text in Chrome :- ( --Jan Kameníček (talk) 22:06, 15 June 2020 (UTC) @Jan.Kamenicek: in your file, for me in both Chrome and Firefox the lines 2 and 3 look the same, and different to line 1. Working as expected. ”

“ You can follow whomever you wish. -- George Orwell III (talk) I also figured the problem is an mw. update, but couldn't understand why only for some users and not others. NOTE#4: Don't know this yet for sure. It could be all the "outdated" gadgets you're loading as well. Ineuw's reply to NOTE #4: I have No gadgets, my common.js was set up by you.
HERE is where it said you have gadgets loading. -- George Orwell III (talk) 06:33, 17 August 2014 (UTC)
I copied the Firefox element inspector results HERE. It seems to me that load.php missed loading three scripts. ”

“ There is nothing wrong about displaying the style characteristics of individual works in general. With works displayed in the main namespace, and changing the available default layouts, there is a problem with the browsers. Serif appears smaller than non-serif, (Times New Roman or Garamond versus Arial) , because of the stroke thickness of some crucial characters, even though they are the same font size. Both Chrome/Chromium and Firefox allow only one size setting for both. I can't speak for the font settings of Safari, Opera, Edge, or Internet Explorer. ”

“ IE11 was the only browser displaying 19 lines of text all the others were 25 rows.I also spent an inordinate amount of time figuring out the font style and font issue. Firefox has its own fonts built in and are inaccessible. I suspect the same with Opera and Chrome.— Ineuw talk 00:03, 15 February 2015 (UTC)
In your screenshots you appear to have toggled the page scan to appear above the edit box and tools. I get the impression that the box is as long as it is because it is meant to stretch a distance downward comparable to a page scan shown beside it. ”

“ I've been swearing over random F/F freezes (Linux/Vector) over much the same period as well. AuFCL (talk) 09:17, 3 July 2014 (UTC) I get "script errors" here asking me if I want to continue with the script or not. I have Firefox 30.0 - but then again, not long ago before the automatic Firefox upgrade, I lost 1/2 of my editing bar - the part I never used anyhow except enlarge, reduce image &c. which I can do another way. —Maury (talk) 15:24, 3 July 2014 (UTC) ┌─────────────────────────────────┘
@William Maury Morris II:I received notice that this has been fixed. ”

“ Yes, yes—is a very dangerous thing!
Suspecting Mediawiki:common.css might not be loading fully, I took the liberty of copying the content of (your) User:George Orwell III/common.css/dynimg.css locally to my local desktop; and then used Firefox's Web Developer Extension's capability of force-loading a local CSS image after viewing our friend Template:FreedImg/doc. ”

“ The browser should always grab the user's default sans-serif font. The Haz talk 12:28, 5 June 2015 (UTC) Thanks for the explanation. — Ineuw talk 19:00, 5 June 2015 (UTC) Page Checker gadget - page is not directing properly . . . again
Tracked in PhabricatorTask T101097Resolved Please try it— Ineuw talk 21:08, 15 May 2015 (UTC)
Still not working and tried with Firefox for Mac and Safari --kathleen wright5 (talk) 14:33, 17 May 2015 (UTC) Not working in Firefox on Windows 7 for me either. —Beleg Tâl (talk) 20:59, 17 May 2015 (UTC) Who "fixed" it the last time it was not working? ”

“ Wikisource webpages keep on loading non stop Wikisource keeps on loading a page long after it's fully loaded. In Windows 7, this is true with Firefox, Comodo Dragon (Chrome) and Opera, but not with IE 11. Every other website loads and stops normally, including Wikipedia and Wikimedia Commons. This ongoing loading is also in Linux Xubuntu 14.04 Firefox, but not Chromium (Chrome) . ”

“ Additionally, IE renders larger text smaller than other browsers and the proposed solution. Firefox is much closer to the proposed solution, but its {{smaller}} is slightly smaller than proposed. In chrome, the current and proposed sizes are the same (to my eye, at least) . I think it's pretty well known that editors of Wikimedia projects tend to use IE much less than do readers of Wikimedia projects. Hence my concern that editors who use Firefox and Chrome (like me!) are setting fonts to what "looks good" to them, without checking what it looks like for others (especially IE) . ”

“ I did manage to embed a link under the text that points to our main page at least. (Note: syntaxhighlight extension appears to be semi-broken; enclose, style settings have no effect) . -- George Orwell III (talk) 01:58, 25 June 2015 (UTC) @George Orwell III: Firefox 38.0.5 will not display anything when presented with this latest; but will accept (i.e. display and act upon) the linkable image if <svg> attributes height and width are relaxed to (both) values "auto". Does a viewBox set to all zeros even make sense (and if not would it be best to remove the specification?) ”

“ But then again, my display options at Wiktionary frequently change without my selecting anything either. --EncycloPetey (talk) 06:04, 29 January 2016 (UTC) @AuFCL: Remaining question: So, why is it that my default "Display Options" setting on a PC (using Firefox) is with page numbers to the side, but my default setting on the Mac (also using Firefox) is now page numbers in the text? I have not changed any Preferences or selections, but now on a Mac, I have to select the "Display Option" individually for EVERY new work that I view. ”

“ They look different both here and in the Map for me. --EncycloPetey (talk) 03:24, 31 January 2022 (UTC) @EncycloPetey: Thanks for the input, but it also depends on the system font, browser configuration and font selection. I switched to Google Chrome which defaulted to the Linux Mint system font of Ubuntu and Monospace Regular. In this case the characters were displayed properly. Then, installed the Advanced fonts extension and set it to Noto Sans, Noto Serif, and Noto Mono, to conform with the Firefox font configuration and the character was misprinted again. ”