The following discussion has been transferred from Meta-Wiki.
Any user names refer to users of that site, who are not necessarily users of MediaWiki.org (even if they share the same username).
Bugzilla search 
Searching for "wikipedia" on b.m.o in the short description (in advanced mode) with a resolution of "---" returns 12 bugs; a few appear to be dups. The most commonly reported problem appears to be Bug 350684 – Print preview of Wikipedia page hangs if scale factor other than 100%, which may be a dup of bug 266681 – Print preview crashes reproducible on validated (!) CSS 2.0 page. Others worth looking into include:
- General layout problem
- Bug 373427 – enhance: css float+clear similar to IE
- Bug 9101 – Break lines at soft hyphens () and display hyphens if line broken (due to land in ff3)
--Jayvdb 07:24, 2 April 2007 (UTC)
Searching for wikipedia in the URL field returns 144 bugs (unconfirmed, new and dups). wikisource also has one unconfirmed bug. Most of the ones I have found this way are of little consequence to Wikipedia (i.e. trivial rendering issues like bug 338921), but its good to see wikimedia resources are being used as a distributed open-content test-case development system for open-source web-browsers! Jayvdb 09:26, 16 April 2007 (UTC)
Page move 
I think a better approach is to use this page to gather bugs that affect MediaWiki. Once we have enough we can order them in terms of priority and submit the most important 10 bugs to Mozilla as planned. Have reworded intro to this affect. Hope that's OK with everyone. --HappyDog 10:30, 2 April 2007 (UTC)
- Thanks, the new title is much less intimidating. Jayvdb 11:18, 3 April 2007 (UTC)
Firefox 3 
There is one bug in the "Closed" section that is marked as fixed in ff3, Bug 9101 is due to land in ff3, and firefox 3 is exhibiting unconfirmed critical problems rendering km:Main Page (Bug 375012). Do we have a test suite that could be used by Wikipedians to verify that FF3 nightlies work correctly for all required Wikimedia functionality? Jayvdb 13:05, 3 April 2007 (UTC)
Caching problem 
An interesting "feature" that may be relevant here is Bug 154115: does not issue byte-range request to HTTP/1.0 servers [was: Partial caching is broken through Squid proxy.. In short, if a user presses "Stop" and then "Reload" nn4 would continue where it left off, whereas FF starts all over again. This is probably not a major headache for either user or the foundation servers, but maybe there other ways to hit this perf bug (pausing http downloads?).
Squid does not report itself as 1.1 even though it supports the required 1.1 features(Bug 411 and more importantly Bug 412); even when Squid fixes this, it will take time for the squids around the world to be updated. Jayvdb 01:59, 16 April 2007 (UTC)
Unconfirmed bugs 
 link floating away 
- I moved it here from the main page. It is unconfirmed and it happens in Opera as well. — Alex Smotrov 16:34, 17 April 2007 (UTC)
- I've confirmed the bug because it also happens on enwiki so its unlikely to be a specific glitch in the Russian CSS.
- I cant reproduce the overlapping float problem in Opera 9.2, but as it also happens on w:Doom it doesnt belong in the non-Latin section of our buglist. There are a few other minor rendering bugs that I have found in, so I think a new section called "Rendering" is where a bug like this should go.
- Before doing that I want to find the bug recorded to make Firefox's placement of  links to same as Internet Explorer: i.e. on top of the horizontal line.
- btw, the Firefox problems are probably going to be solved on enwiki by bugzilla:1629#c33; i.e. using the dewiki approach of putting the edit link directly to the right of the section name rather than floated to the far right. Jayvdb 23:51, 17 April 2007 (UTC)
End of content from meta.wikimedia.org
Note that the above conversation may have been edited or added to since the transfer. If in doubt, check the edit history.