This page is intended to document known problems that users have encountered when using certain browsers to browse and edit Memory Alpha. Some of these problems could be bugs in the MediaWiki software, while others may be bugs in a browser's behavior. Others might result from improper implementation of certain features on Memory Alpha. If you find some bugs in your browser, please do not report them here, but instead report them to an administrator.
As a matter of course, we recommend that you use the most recent browser version available (that your platform supports). This means the latest (stable) builds of Mozilla, Internet Explorer 6, Opera 7, or Safari. This page is intended to address issues with modern browsers, meaning IE 5 and later, Mozilla/Netscape 6 and later, and Opera 6 and later.
- IE does not automatically refresh style sheets when a page is reloaded; you must empty the cache by pressing CTRL-F5, and then reload the page.
- All versions of IE have problems with text sizes, but should work fine with the default skin. Textboxes may be too wide on other skins, or font sizes may be illegible.
Gecko-based browsers (Mozilla, Firefox, etc.)
- Mozilla 0.9.9 has problems saving forms (such as Memory Alpha edits) longer than about ten Kb; the connection stalls and the page is not saved. Use an older or newer version without the bug.
- Opera 5.05 in 800 × 600-pixel monitor resolution handles the default skin poorly – with objects heavily overlapping. A "no skin" or "MySkin" skin setting is recommended.
- Opera 6's internal memory sometimes cannot handle long pages (i.e. larger than 32 Kb), and mangles the output.
- Opera 6 cannot handle auto-login between browser sessions.
KHTML-based browsers (Konqueror, Safari, etc.)
- Safari has a sixty-second browser timeout, which may be shorter than the amount of time it takes for your edit to be acknowledged, especially if the server load at the time is high. You should not click the "save page" button a second time, because this repeats the edit and consumes additional disk space on the server. You may want to install SafariNoTimeout, a free extension that will increase the sixty-second timeout to ten minutes. Note that this is unnecessary as of Mac OS X 10.3.6.
- OmniWeb 4 occasionally hangs permanently (or crashes) when attempting to save a page.
- OmniWeb 5 will sometimes forget the auto-login preference.
- Ad blockers
- Many ad blockers will block access to pages or images if they contain the string "ad" in them. (This is occasionally a problem when uploaded images are stored in the /ad/ directory, for example.) This problem has been reported in Opera (kiosk mode), Atguard, Norton Internet Security, and WebWasher. Outpost Firewall also has a similar feature, but its behavior can necessarily be configured.