Wikipedia talk:Browser notes

message: ----
I have had some trouble logging in.  This is probably a browser problem for Safari users (Safari has problems with this site!).  Too bad for us Safari users.  --66.47.86.47 13:52 Feb 23, 2003 (UTC)
:Safari is based on the Konqueror HTML rendering engine, I don't know whethter that encompases such things as login/cookie management, but everything works fine under Konqueror - maybe you could describe your problems more acurately. --snoyes 15:04 Feb 23, 2003 (UTC)
Here's a more indepth description:  When I go to the login page and type in my user name and password and click "login", red lettered words inform me that my user name does not exist.  At other times I can login with no problem.  --66.47.86.47 15:59 Feb 23, 2003 (UTC)
:: see Wikipedia:Browser notes & leave a note there -- Tarquin 15:06 Feb 23, 2003 (UTC)
:Sign-on with Safari for Windows, version 3.0.2 (522.13.1) worked fine for me.  Perhaps you were using a different version and/or OS?  The OS and version information will also help to place the comments in the right section of this article.Mwarren us 00:31, 11 July 2007 (UTC)
thread_title:  Safari problems 

message: Moved from Wikipedia:Village pump on Tuesday, July 8th, 02003.
Current Events doesn't render properly in Safari - the text goes over the sidebar.  I don't know enough HTML to consider editing...  Also, I found that typing Loma-Prieta in the search bar brings up the Mira Loma entry, even though there is a Loma-Prieta page (it was empty, so I changed it to a redirect to Loma Prieta - oh, I just realized it should have been Loma Prieta Earthquake!). Anyway, the search behaved the same both before and after I added the redirect to the page. -Aion 18:58 5 Jul 2003 (UTC)
:Safari renders all pages here at Wikipedia just fine.  The only thing that does not work is when you make the page too small from left to right.  Then the text in the upper right region overlap the left column.  Drag the Safari window bigger (the horizontal size) and see if that fixes things.  Also, are you using the latest Safari 1.0 (v85)?  As I said, Safari works fine for me at Wikipedia. Good luck.  --Mahongue 02:02 6 Jul 2003 (UTC)
:There was an HTML error on the Current events page, which I've now fixed. Does it render properly now? --Zundark 19:23 5 Jul 2003 (UTC)
::No, it's still the same.  It looks like maybe the "Hong Kongese constitutional changes" item is setting the width of the sidebar to be too wide?  It renders properly in IE, and Netscape, though.  So it might be a Safari problem. -Aion 21:15 5 Jul 2003 (UTC)
:::Putting 'loma prieta' in the search box and hitting 'go' brings up Loma Prieta earthquake for me. Current events looks fine in Safari 1.0 for me, though if you shrink the window down real small of ourse you get problems. More detail please? --Brion 22:06 5 Jul 2003 (UTC)
End moved discussion.
----
Help! Is there any browser out there that doesn't screw up something on wiki? IE does bizarre things to some pictures, won't go into pages over 32K (or rather chops the end off) and turns  captioned text into spidery unreadable stuff, Netscape won't recognise  at all, putting all text into the same size (which sort of f**ks up captions carefully laid out using the commands), safari is brilliant but times out after 60 seconds (which means that 4 times out of 5 lately on wiki it fails to enter a page, change a page, etc). I thought camino was fail-safe but no, now I find that it too won't accept the  command. It is as if the designers of these things all get a perverted pleasure in putting some little glitch just to annoy users. :-) Is there anything out there for a mac that doesn't chop pages, muck up captions, move around pictures or time out after a minute? FearÉIREANN 02:22 7 Jul 2003 (UTC)
:A minimal test page for  looks ok for me in Mozilla 1.4 and Camino 0.7... Can you point to a specific page that's problematic? --Brion 02:41 7 Jul 2003 (UTC)
Short answer: No. There is no perfect browser. But Mozilla and Opera seem to be the least prone to weirdness, in my experience. -- Wapcaplet 02:52 7 Jul 2003 (UTC)
I always use Mozilla 1.3 on Mac OS X.  I suspect that it randomly inserts newlines sometimes in edit boxes, but pics and html and exotic fonts all seem to work fine. Stan 03:22 7 Jul 2003 (UTC)
See Wikipedia:Browser notes, if you haven't already. You can look for browsers with no problems reported and report the problems you have encountered not already listed there. --Ellmist 03:59 7 Jul 2003 (UTC)
----
The article Chives doesn't look right in Mozilla.  The separation line cuts the right-hand size table into halves. It is not the only articles with such problem. Wshun
:This behavior seems to be triggered by going into standards compliant mode... if I break the doctype to put it in quirks mode, the  will not pass through the floated box. Hopefully there's a sane way to work around this. :P
:Bug is listed at bugzilla, supposedly there's a patch in the works.
:As a workaround, I've patched our JavaScript bits to hack the CSS to revert just  to the quirks mode handling if you're running a Gecko-based browser. :P  Hit reload to get the new code. --Brion 04:32 10 Jul 2003 (UTC)
----
Opps, Brion, sorry I forgot to come back and tell you about the problem with Camino not recognising the </small. command. Quite simply it never ever recognises it. For example Papal Tiara, James I of England. Also the top of the Recent Changes page. FearÉIREANN 02:00 15 Jul 2003 (UTC)
 wearing the 1834 Triple Tiara of Pope Gregory XVI
(running a test here!) 
The above for example, irrespective of whether the  commands are in or simply the middle line is used here, appears as large italics on Camino 0.7 but small italics on IE. (Good God. I knew if I wated long enough I'd find something good to say about Explorer. So it isn't 100% crap, merely 95%! FearÉIREANN 02:00 15 Jul 2003 (UTC)
:That might explain why Camino's not yet up to version 1.0. ;) - Hephaestos 02:07 15 Jul 2003 (UTC)
:Looks fine to me... OS X 10.2.6, Camino 0.7. --Brion 05:15 15 Jul 2003 (UTC)
:
I've discovered a bit of the problem. Camino + Cologne Blue together don't show small!!! I was using Cologne Blue. :-(  So I guess that leaves me with the problem of which do I chose - nice skin + IE (aaaaaagh!) or yuch skin + camino (aaaaagh!) Maybe I'll sleep on it. BTW, re the floating quickbar, does it ever actually float??? :-) FearÉIREANN 05:51 15 Jul 2003 (UTC)
:Reload the page and you should find the  tags operating as expected under Cologne Blue. Apparently for reasons unclear, using an absolute point size for the text (eg, font-size: 10pt) causes the smallish effect of the  tag to become very very slight in Camino (and hence unnoticable at 10pt). Putting an explicit small { font-size: 75%; } into the style sheet declaration makes it work more as expected:
:
:As far as the floating quickbar; Cologne Blue really isn't set up for that, so you just get the boring one that's stuck at the top of the page when you scroll. Sorry. --Brion 06:19 15 Jul 2003 (UTC)
I am not a font expert, but isn't this a simple case of not having the appropriately-sized bitmap font? If Camino defines "small" to mean "80%-size", and your bitmapped font has, say, 16 pixel and 10 pixel sets, and your normal font is 16 pixels, 80% would come out to 12.8 pixels, which might just be rounded up to 16 pixels again (purely hypothetical, of course, but you see my point). Does the lack-of-small problem occur with all font sizes? What happens if you zoom in/out, or choose a different "default" font in your preferences? (if Camino has such capabilities - I haven't used it). -- Wapcaplet 11:24 15 Jul 2003 (UTC)
:Bit map fonts? MacOS X does not understand your strange terminology, it's all magic vector truetype display PDF smoothy anti-aliased crud. ;) Defining 80% also works fine, while pumping the font zoom up to HUGE shows only the tiniest of visible changes without the explicit percentage definition. --Brion 16:24 15 Jul 2003 (UTC)
::Clearly I am no Mac expert either ;-) I suppose my next question would be, has anyone actually measured the height of the "small" font in pixels? Could just be a quirk of human visual perception that 80% looks too similar to 100% for some fonts. -- Wapcaplet 23:56 15 Jul 2003 (UTC)
:::No, the trouble is the way that it handles the 'smaller' font size keyword, which is specified for the  tag in Mozilla's default style sheets. It's not a percentage value (which works fine if we force it, be it 75% or 80% or whatever), rather it ratchets down to the next-smaller value in a fixed list. Certain values are particularly bad: 10pt translates to something like 13.33 pixels, and so it picks the next-smaller size of... 13 pixels! If you zoom the text size way up in Camino, the 0.33 difference turns into a couple of whole pixels and is visible, but at normal size the font scaling rounds the 10pt text to 13px, the same as the "smaller" text. See bugs 72164 and 201811 in bugzilla. This may be fixed in more recent versions; but Camino hasn't updated (at least not in release versions) and I haven't tested the just-released Mozilla 1.4 (nor will I have a chance to for a while). --Brion 01:41 16 Jul 2003 (UTC)
----
Opera 7.20 -- I recently downloaded the new opera 7.20 browser, and while normal pages appear just fine, the main page is all screwed up -- the tables don't seem to align properly. Thoughts? Brassratgirl 00:51, 6 Oct 2003 (UTC)
thread_title: Current Events bug in Safari

message: Since using iCab 2.97 on my iBook (running Mac 10.2.8) I have been unable to view the Hebrew in the Bible translations article. I've tried with MSIE 5.2.3 and the Hebrew doesn't work. It works with Mozilla and Safari. Also, the 'hide' in the table of contents box is hidden. Can anyone confirm these things?
- iHoshie 06:26, 22 Dec 2003 (UTC)
thread_title:  Problems with iCab--Can anyone confirm? 

message: Hello, I use an updated version of IE on a quite updated previous century GUI OS from Redmond, WA, and after I started using the 'new default skin' (?) after the recent server installs, both stub links and broken links display the same -- as red links. Before, with the 'yellow' skin ('standard'?), stubs had a brownish color while only broken links were red. Could somebody help me out here? (or point me to a more relevant place to get help?). I have already checked several hopefully relevant FAQs but to no avail. --Wernher 18:25, 1 Jun 2004 (UTC)
replies: text: It seems to be allright now (has been for some time, starting a couple of days after my posting above). --Wernher 15:55, 12 Jun 2004 (UTC)
thread_title:  Stub lks display like broken lks 

message: I'm adding Mozilla Firefox and Mozilla itself to the list of supported browsers with "no problems" for Unix/Linux.  I'm certainly having no problems with them.  (Mozilla 1.4, Firefox 0.9.1 here)  --Ardonik 03:47, 9 Jul 2004 (UTC)
replies: text: Version numbers for the Firething and lizard are imperative: older versions of Gecko have serious CSS implementation failures which affect the new standard Wikipedia skin. But Gecko 1.4 seems to work relatively good on Windows also. Anárion 09:07, 9 Jul 2004 (UTC)
thread_title:  Firefox and Mozilla are OK? 

message: The Link http://en.wikipedia.org/wiki/Wikipedia:Browser_notes#Textarea_tools included on Help:Contents as "How to edit with an external editor". However this page doesn't contain any information about how to use an external editor with wikipedia. What I expected to find was information about syntax highlighting for different editors and such.
--Ados 12:51, 12 Aug 2004 (UTC)
replies: text: Something like works for most Wikis. It found it trivial to adapt this synthighligh for SciTE. Anárion 13:07, 12 Aug 2004 (UTC)

text: There's also  an article dedicated to the topic on Wikipedia. I changed the link on Help:Contents to that page. Seems like the more appropriate place to put it. --Ados 14:16, 12 Aug 2004 (UTC)
thread_title:  How to edit with an external editor 

message: Is it just me, or does the editing toolbar not appear in Safari?  I'm using Safari 2.0.2 (416.12) on Mac OS X 10.4.3.  I also have PithHelmet, but the toolbar doesn't appear even when I reload the page unfiltered.  --Kenyon 22:09, 22 November 2005 (UTC)
replies: text: The toolbar can be disabled in the Wikipedia preferences (I do not see it as well). Maybe this is the problem. I also think that JavaScript must be enabled for it to work. Paolo Liberatore (Talk) 17:06, 23 November 2005 (UTC)
replies: text: The toolbar is enabled in my preferences.  It works in Firefox on my Linux machine.  JavaScript is enabled in my Safari prefs.  Still no toolbar in Safar.  Strange... --Kenyon 03:08, 3 December 2005 (UTC)
thread_title:  No editing toolbar in Safari? 

message: I'm surprised this hasn't been noted here before (or it just me!?), but I've noticed that Firefox seems to ignore automatic separation between image and tables/text in Wikipedia articles. This causes some images to overlap text and tables. (For an example, see the Wikipedia article, Timeline of glaciation. There is a difference between how that article shows up in Firefox and IE - look at the first image and table.) Yet, when I open Wikipedia articles in IE, images and tables/text are automatically separated as they should be. I haven't been able to find any troubleshooting references to this here in Wikipedia, unless I've missed something. While I do know that this overlap problem can be resolved by changing the size of images as they show in the articles, some may not want to go to the trouble or even know how to deal with this irksome problem. (I have left that first image size deliberately unedited in the example article mainly to illustrate this problem) Is Wikipedia working on this problem of Firefox ignoring automatic separation between image and tables/text? NorthernFire 20:15, 15 February 2006 (UTC)
replies: text: The  answer to that is, quite literally: it's not a bug, it's a feature.  CSS boxes are allowed to overlap, which is good, because they're boxes, and so anything else would result in oddity.  Consider the checkmark at the right: its box overlaps this paragraph's box.  Fortunately, this paragraph is nice and flexible, so it can flow around the checkmark; tables aren't so flexible, so they can't.  Start points of blocks are fixed by their position and attributes; you can't just shove around blocks with clear: none.  IE does, and in this respect it does not comply with standards.(Note: the above is correct to the best of my knowledge; my proficiency in CSS is moderate.  But see Mozilla Bug #241,031.) —Simetrical (talk • contribs) 15:14, 19 June 2006 (UTC)

text: Someone on the #wikipedia IRC channel has just informed me that the same "bug" occurs in Opera 9. —Simetrical (talk • contribs) 15:24, 19 June 2006 (UTC)
thread_title: Problems with image/text layout in Mozilla Firefox

message: I'm removing some text from the Internet Explorer section. Much of it is vague or doesn't even make sense (or perhaps just no longer applies). I am currently using IE6 on XP, SP2.
Perhaps most annoying are not the times when content doesn't appear in IE, but the times when Microsoft has gone out of their way to ensure that it does appear where other web browsers have stuck to the standards—see this revision for an example of what can occasionally result.  More instances follow.
:I don't think the beginning makes sense. Also, the given revision and the previous (and next) revisions look exactly the same to me, layout-wise. Overall, though, this should probably be put back with a concrete example.
IE cannot handle numeric character references (NCRs) in UTF-8: if a page uses this encoding and NCRs the encoding must be set to User Defined.
:I've tried various websites and Wikipedia pages, and I think NCRs work fine for me.
Ardric47 02:24, 10 July 2006 (UTC)
thread_title:  IE stuff 

message: There is no mention of Crazy Browser here. Anyone with information about this browser is welcome to add in the details here. --Siva1979Talk to me 03:19, 1 September 2006 (UTC)
replies: text: It seems to be just an IE shell, not a true distinct browser; as such, it probably has no rendering differences. *Dan T.* 22:37, 23 September 2006 (UTC)
thread_title:  Crazy Browser? 

message: If you take a look at Serie A there should be a table half way down detailing the results of the season so far.  In IE, it is perfect, with the names along the top being shown vertically.  But in Firefox, the names are being shown horizontally accross the page making the table far to wide when using firefox.  Any fixes ? Niall123 22:21, 23 September 2006 (UTC)
thread_title:  Problem with Firefox 

message: Opera 8.54 on Win98SE here. I'm getting a sporadic error editing large pages, usually data tables and such, where  gets replaced with >sup>, or colspan="2" with colspan="2" for example. Anybody else gets these glitches? Femto 11:27, 17 October 2006 (UTC)
thread_title:  Opera, symbols to escaped HTML entities 

message: Anyone else having trouble with alt-e and alt-s not editting pages but instead going to the Firefox Edit menu with 2.0?  I just noticed this tonight (I think this is the 1st time I've tried in 2.0).  Could be something dumb I've done or could be 2.0 issue. -Jcbarr 05:49, 16 November 2006 (UTC)
thread_title:  Firefox 2.0 and shortcut keys? 

message: They appear below the text. See the screenshot of Toronto Raptors here: http://img95.imageshack.us/my.php?image=ffyg9.png —The preceding unsigned comment was added by MC (talk • contribs) 00:24, 5 May 2007 (UTC)
thread_title:  superscripts arent super in Firefox 

message: Wouldn't it make much more sense to order the browsers according to the used rendering engine?
Shouldn't the exact number of the version of the browser (and the version number of the rendering engine if available) which causes the problem also be cited?
Example of ordering:
Mac OS X
WebKit based
* Safari
* OmniWeb 4.5+
* iCab 4.0+
* Shiira
Gecko based
* Mozilla Firefox
* Netscape
* Mozilla Suite
* Seamonkey
* Camino
Elektra based
* Opera 4 to Opera 6
Presto based
* Opera 7+
iCab prior to 4.0
OmniWeb prior to 4.5
--Liebeskind (talk) 18:57, 19 July 2008 (UTC)
replies: text: Be bold and do it!  -- Avocado (talk) 19:46, 19 July 2008 (UTC)
thread_title:  Order of Browsers 

message: This seems to show artcile pages differently as from today with the inforbox on top of the artcile rather than at the side.  If I swicth to IE it displays normally.  Apologie sif not right place, but I am not sure whether this is a Wiki chnage or the new Firefox version.? Jezhotwells (talk) 16:36, 7 July 2009 (UTC)
thread_title:  Firefox v3.0.11 

message: I cant't update long articles on my new laptop Acer. I have a fast Adsl conection through ethernet cable. Do I have to change some setting ?
When I save the article after some time of waiting the session is cancelled.
MSacerdoti  —Preceding unsigned comment added by MSacerdoti (talk • contribs) 07:28, 22 April 2010 (UTC)
thread_title:  Explorer 8 with Windows 7 

message: I have understood some browsers has limitions with page size. I hope someone can give an input on archive page size discussions based on current technology situation. --Kslotte (talk) 13:36, 4 September 2010 (UTC)
thread_title:  Archive page size 

message: Hi,
For Linux ... Dillo, "Cookies are tricky, so logging in is tricky".
Thanks for the warning. =8~/ Someone who has succeeded to log in, please give tips to resolve the trickiness. Can an image be uploaded to Commons using Dillo?
Background
For several years I've used Firefox in Debian. Recently, probably since an upgrade, Firefox crashes frequently reporting "channel error". A documented bug.
This afternoon information for two uploaded images was almost complete when Firefox vanished from the screen. Troubleshooting Firefox will be a goose chase which may never succeed. At this rate the project may never be completed. If Dillo can work, good. It's fast. It isn't bogged with JavaScript.
Thx, ... PeterEasthope (talk) 23:01, 15 September 2022 (UTC)
thread_title:  Dillo 

message: my lynx version: 2.9.0dev.6-3~deb11u1 on debian bullseye. i have enabled color profile of lynx.lss on lynx.cfg & copy pasted code given on lynx.lss, both located at /etc/lynx/. is this issue for current version? <_>jindam, vani (talk) 05:58, 8 October 2022 (UTC)
thread_title:  lynx.lss settings not working 

message: i did ask on lynx-dev mailing list about 
diff pages: assign or view colors on INS: or DEL: on wikipedia diff page with the below settings (provided by Thomas Dickey at lynx-dev mailing list) in lynx.lss, you can 
view diff pages similar to gui browsers.
ins:            reverse:                green
del:            reverse:                red
the above settings working for me on Lynx Version 2.9.0dev.10 (11 Aug 2021)
libwww-FM 2.14, SSL-MM 1.4.1, GNUTLS 3.7.7, ncurses 6.2.20201114(wide)
Built on linux-gnueabihf.
lets hope this will bring more users..... <_> Jindam vani (talk) 14:41, 19 October 2022 (UTC)
thread_title:  (knowledgebase) viewing of diffs on lynx: lynx.lss settings