The factual accuracy of this Wikipedia page may be compromised due to out-of-date information. Please help update this Wikipedia page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. |
Browser notes is a Wikipedia page aimed at helping contributors and readers learn of issues with various web browsers. It addresses what kind of issues users are facing .There is no perfect browser for viewing Wikipedia.
Please list the pros and cons of particular browsers for viewing and editing Wikipedia articles. Limit your contributions to practical drawbacks and actual experiences with various browsers in interaction with Wikipedia. If you wish to report a bug to do with Wikipedia's interaction with a browser, see Wikipedia:Bug reports and feature requests.
No browser wars, but if you must comment at length, take it to the Browser notes talk page, please.
Please change the order of the browsers to place the Consensus Best Browser first on the list for each platform and continue in order of preference. Keep comments brief.
Most browsers support a direct interface for searching Wikipedia. See Help:Searching for more information.
Old versions of IE demonstrate poor support of relatively recent (e.g., post-1999) W3C Web standards, but are still in use. As a result, certain elements may not look or work exactly right, although generally a workaround of some kind is implemented server-side if possible. Among the most visible issues are:
<q>...</q>
tag with quote marks.OmniWeb is no longer maintained, but is still available for download.
Also has been discontinued.
.org ACCEPT
Warning: Many console browsers will convert text in edit boxes to the encoding in use by your terminal (or what the browser thinks is your terminal's encoding which may not be the same thing) either at page load time (links and lynx) or when editing a field (w3m). If your terminal encoding is UTF-8 this is not a problem but if your terminal is using a legacy encoding (or is using UTF-8 but your browser thinks it's using a legacy encoding) then this is likely to destroy characters that are not present in the encoding your terminal is using when you save the page after editing.
/*
1. place in ~/.elinks
2. set user css to be "user.css" (no path, relative to ~/.elinks)
3. use document colors: use 1 or 2
*/
.diffchange {
color: red;
font-weight: bold;
}
.diff-deletedline {
color: green;
}
.diff-addedline {
color: cyan;
}
a.new {
color: cyan;
font-weight: bold;
}
--[[
lua preformatting function
1. lua has to be installed before compiling elinks; if this
is the case, it is used by default
2. place this file in ~/.elinks
this file does:
show <del> and <ins> element, make <s> more evident
preformatting for wikipedia pages: since elinks ignores the
class attribute of <td> tags, we move it into the inner
<div> element
]]
testing=false
function pre_format_html_hook (url, html)
-- formatting for <s> <del> <ins>
html = string.gsub(html, '<[sS]>', '<s>[S:')
html = string.gsub(html, '</[sS]>', ':S]</s>')
html = string.gsub(html, '<[dD][eE][lL]>', '<s>[DEL:')
html = string.gsub(html, '</[dD][eE][lL]>', ':DEL]</s>')
html = string.gsub(html, '<[iI][nN][sS]>', '<s>[INS:')
html = string.gsub(html, '</[iI][nN][sS]>', ':INS]</s>')
-- diff-addedline and diff-deletedline classes
if string.find(url, "diff=", 1, 1) or testing then
html = string.gsub(html, '<td class="diff[-]addedline"><div>',
'<td><div class="diff-addedline">')
html = string.gsub(html, '<td class="diff[-]deletedline"><div>',
'<td><div class="diff-deletedline">')
end
return html
end
lynx.lss
configuration file:
See: Wikipedia:Wikipedia on PDAs and Help:Mobile access.
Some
browser extensions are not fully compatible with Wikipedia or may have unwanted effects. Some extensions add text like when editing <div class="myEventWatcherDiv">
, QuickiWiki Look Up
or <a class="ktg6us78hf8vdu7" href="javascript:void(0)">
. Most of these are detected by
Edit Filter 345 which issues a warning message.
[[foo]]
to [foo-en]
or [[foo|bar]]
to [foo|bar-en]
(
discussion).Plugins that can be used to search Wikipedia more easily.
Safari→Services→Unicode→
), or keyboard shortcut (command-shift-8
).The latest version (3.0 from 1997) of NCSA MOSAIC will not load Wikimedia pages due to lack of support for the HTTP 1.1 host header system.
NetPositive ran only on BeOS. Not all elements of the CSS recognized, though still fairly functional. NetPositive has issues with some HTML entities on repeated editing (replacing entities by the character glyph), so be careful.
The very old Netscape Navigator, cannot edit long pages. See Wikipedia:Article size.
On Unix in version 4.x: Problems with <div> marked images; sometimes crashes when one writes a new article or heavily edits an existing one.
On Mac OS in version 4.5: overlapping text and quick bar under cologne blue settings, may add weird space in text; some encoding issues.
Internet Explorer for Mac OS X runs only on classic Mac OS.
Side toolbar appears in wrong location (below any main text).
Prior to Firefox 2, the find-as-you-type text search ignored the edit window. Bugzilla@Mozilla bug 189309 documents the issue, which does not occur in the newer version, Firefox 3.
Prior to Firefox 3, when editing, Firefox changed all non-breaking spaces ( hexadecimal 0xA0) to breakable spaces (hexadecimal 0x20). Bugzilla@Mozilla bug 218277 documents the issue, which does not occur in the newer version, Firefox 3.
Safari on Windows renders fonts using its own algorithm that yields results differing slightly from the native Windows font renderer. [1]
Default settings
Cologne Blue
User installed style-sheets
#column-content { margin: 0 0 0 0; line-height: 1em; float: none; } #content { margin: 0.0em 0 0 0; /* Change the 0.0em to 2.8em to make */ /* extra white space at the top of a wiki page */ /* The 0.0em causes the tab buttons at */ /* the top ("edit this page", etc) to disappear */ /* on gecko based browsers. In such a situation hit */ /* "alt+shift+e" to edit this page */ line-height: 1em; padding: 0 0 0 0.2em; } /* Something about the above two sets of lines makes all content flow */ /* linearly down the page */ #column-one { padding-top: 0px; line-height: 1em; } #p-logo { position: relative; } #globalWrapper { font-size: 100%; /* Sets all fonts to normal size */ line-height: 1em; } #contentSub { font-size: 100%; /* Sets all fonts to normal size */ margin: 0 0 0 0; /* Removes margins */ line-height: 1em; color: #FFFFFF; /* Sets the background to white */ } ul, ol, li, dt, dd, p, h1, h2, h3, h4, h5, h6 { line-height: 1em; } /* Packs lines nicely*/ div.tright, div.tleft { border-width: 0 0 0 0; line-height: 1em; padding: 0 0 0 0; } /* Shrinks thumb picture frames as much as possible. */ div.thumb div div.thumbcaption { line-height: 1em; padding: 0 0 0 0; } /* Shrinks thumb picture frames as much as possible. */
The factual accuracy of this Wikipedia page may be compromised due to out-of-date information. Please help update this Wikipedia page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. |
Browser notes is a Wikipedia page aimed at helping contributors and readers learn of issues with various web browsers. It addresses what kind of issues users are facing .There is no perfect browser for viewing Wikipedia.
Please list the pros and cons of particular browsers for viewing and editing Wikipedia articles. Limit your contributions to practical drawbacks and actual experiences with various browsers in interaction with Wikipedia. If you wish to report a bug to do with Wikipedia's interaction with a browser, see Wikipedia:Bug reports and feature requests.
No browser wars, but if you must comment at length, take it to the Browser notes talk page, please.
Please change the order of the browsers to place the Consensus Best Browser first on the list for each platform and continue in order of preference. Keep comments brief.
Most browsers support a direct interface for searching Wikipedia. See Help:Searching for more information.
Old versions of IE demonstrate poor support of relatively recent (e.g., post-1999) W3C Web standards, but are still in use. As a result, certain elements may not look or work exactly right, although generally a workaround of some kind is implemented server-side if possible. Among the most visible issues are:
<q>...</q>
tag with quote marks.OmniWeb is no longer maintained, but is still available for download.
Also has been discontinued.
.org ACCEPT
Warning: Many console browsers will convert text in edit boxes to the encoding in use by your terminal (or what the browser thinks is your terminal's encoding which may not be the same thing) either at page load time (links and lynx) or when editing a field (w3m). If your terminal encoding is UTF-8 this is not a problem but if your terminal is using a legacy encoding (or is using UTF-8 but your browser thinks it's using a legacy encoding) then this is likely to destroy characters that are not present in the encoding your terminal is using when you save the page after editing.
/*
1. place in ~/.elinks
2. set user css to be "user.css" (no path, relative to ~/.elinks)
3. use document colors: use 1 or 2
*/
.diffchange {
color: red;
font-weight: bold;
}
.diff-deletedline {
color: green;
}
.diff-addedline {
color: cyan;
}
a.new {
color: cyan;
font-weight: bold;
}
--[[
lua preformatting function
1. lua has to be installed before compiling elinks; if this
is the case, it is used by default
2. place this file in ~/.elinks
this file does:
show <del> and <ins> element, make <s> more evident
preformatting for wikipedia pages: since elinks ignores the
class attribute of <td> tags, we move it into the inner
<div> element
]]
testing=false
function pre_format_html_hook (url, html)
-- formatting for <s> <del> <ins>
html = string.gsub(html, '<[sS]>', '<s>[S:')
html = string.gsub(html, '</[sS]>', ':S]</s>')
html = string.gsub(html, '<[dD][eE][lL]>', '<s>[DEL:')
html = string.gsub(html, '</[dD][eE][lL]>', ':DEL]</s>')
html = string.gsub(html, '<[iI][nN][sS]>', '<s>[INS:')
html = string.gsub(html, '</[iI][nN][sS]>', ':INS]</s>')
-- diff-addedline and diff-deletedline classes
if string.find(url, "diff=", 1, 1) or testing then
html = string.gsub(html, '<td class="diff[-]addedline"><div>',
'<td><div class="diff-addedline">')
html = string.gsub(html, '<td class="diff[-]deletedline"><div>',
'<td><div class="diff-deletedline">')
end
return html
end
lynx.lss
configuration file:
See: Wikipedia:Wikipedia on PDAs and Help:Mobile access.
Some
browser extensions are not fully compatible with Wikipedia or may have unwanted effects. Some extensions add text like when editing <div class="myEventWatcherDiv">
, QuickiWiki Look Up
or <a class="ktg6us78hf8vdu7" href="javascript:void(0)">
. Most of these are detected by
Edit Filter 345 which issues a warning message.
[[foo]]
to [foo-en]
or [[foo|bar]]
to [foo|bar-en]
(
discussion).Plugins that can be used to search Wikipedia more easily.
Safari→Services→Unicode→
), or keyboard shortcut (command-shift-8
).The latest version (3.0 from 1997) of NCSA MOSAIC will not load Wikimedia pages due to lack of support for the HTTP 1.1 host header system.
NetPositive ran only on BeOS. Not all elements of the CSS recognized, though still fairly functional. NetPositive has issues with some HTML entities on repeated editing (replacing entities by the character glyph), so be careful.
The very old Netscape Navigator, cannot edit long pages. See Wikipedia:Article size.
On Unix in version 4.x: Problems with <div> marked images; sometimes crashes when one writes a new article or heavily edits an existing one.
On Mac OS in version 4.5: overlapping text and quick bar under cologne blue settings, may add weird space in text; some encoding issues.
Internet Explorer for Mac OS X runs only on classic Mac OS.
Side toolbar appears in wrong location (below any main text).
Prior to Firefox 2, the find-as-you-type text search ignored the edit window. Bugzilla@Mozilla bug 189309 documents the issue, which does not occur in the newer version, Firefox 3.
Prior to Firefox 3, when editing, Firefox changed all non-breaking spaces ( hexadecimal 0xA0) to breakable spaces (hexadecimal 0x20). Bugzilla@Mozilla bug 218277 documents the issue, which does not occur in the newer version, Firefox 3.
Safari on Windows renders fonts using its own algorithm that yields results differing slightly from the native Windows font renderer. [1]
Default settings
Cologne Blue
User installed style-sheets
#column-content { margin: 0 0 0 0; line-height: 1em; float: none; } #content { margin: 0.0em 0 0 0; /* Change the 0.0em to 2.8em to make */ /* extra white space at the top of a wiki page */ /* The 0.0em causes the tab buttons at */ /* the top ("edit this page", etc) to disappear */ /* on gecko based browsers. In such a situation hit */ /* "alt+shift+e" to edit this page */ line-height: 1em; padding: 0 0 0 0.2em; } /* Something about the above two sets of lines makes all content flow */ /* linearly down the page */ #column-one { padding-top: 0px; line-height: 1em; } #p-logo { position: relative; } #globalWrapper { font-size: 100%; /* Sets all fonts to normal size */ line-height: 1em; } #contentSub { font-size: 100%; /* Sets all fonts to normal size */ margin: 0 0 0 0; /* Removes margins */ line-height: 1em; color: #FFFFFF; /* Sets the background to white */ } ul, ol, li, dt, dd, p, h1, h2, h3, h4, h5, h6 { line-height: 1em; } /* Packs lines nicely*/ div.tright, div.tleft { border-width: 0 0 0 0; line-height: 1em; padding: 0 0 0 0; } /* Shrinks thumb picture frames as much as possible. */ div.thumb div div.thumbcaption { line-height: 1em; padding: 0 0 0 0; } /* Shrinks thumb picture frames as much as possible. */