Last modified: 2013-02-01 14:02:11 UTC
The editing page for [[:yi:גריכישער אלפאבעט]] does not load on a Mac. It causes the browser to hang. Seems to work ok on other platforms. No idea why.
https://yi.wikipedia.org/w/index.php?title=%D7%92%D7%A8%D7%99%D7%9B%D7%99%D7%A9%D7%A2%D7%A8_%D7%90%D7%9C%D7%A4%D7%90%D7%91%D7%A2%D7%98&action=edit loads fine for me in Firefox 11 and Safari 5.1.5 on Mac OS X 10.7.3.
asking amir and spqrobin to look at this if it comes up again, but closing WORKSFORME re: brion's testing. Please re-open if you can provide more information that you think would allow us to reproduce the problem.
Works for me on Windows, but i'll go the extra mile: Percy Mett, is this article still broken? Can you load other articles with audio links, for example https://yi.wikipedia.org/wiki/%D7%9E%D7%90%D7%A1%D7%A7%D7%95%D7%95%D7%A2 ?
Audio links is not the problem. I agree that the page opens fine under Windows and Mac OS X 10.7 I am having problems under Mac Os X 10.6.8 It opens fine with Firefox and Opera. But Chrome cannot open the page. And Safari hangs when trying to open it. Sorry I wasn't clearer in the initial report.
Thank you for the clarification, Percy. Just making sure: Does it open in Chrome or Safari on Mac OS X 10.7?
Also, can you open other pages? Can you open pages in other languages? Is it just this particular page that crashes?
(Reopening, because there may be an issue here.)
(In reply to comment #5) > Thank you for the clarification, Percy. > > Just making sure: Does it open in Chrome or Safari on Mac OS X 10.7? Both OK on Mac OS X 10.7
(In reply to comment #6) > Also, can you open other pages? Can you open pages in other languages? Is it > just this particular page that crashes? I don't think I have any problems with other pages in Yiddish or any other language
(In reply to comment #6) > Also, can you open other pages? Can you open pages in other languages? Is it > just this particular page that crashes? I have noticed that page yi:גריכנלאנד displays the same (mis)behaviour.
I guess that issue has been solved, I do not have that problem with Safari 6.0 and Mac OS X 10.7. I am assuming that was an upstream bug in webkit.