Closed Bug 184566 Opened 22 years ago Closed 22 years ago

Navigator/Omniweb (any cocoa based app) not responding to external URLs in some configs.

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: cosm7x, Assigned: saari)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021206 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021206 Chimera/0.6+

This is not a chimera specific bug, but it affects chimera along with other
cocoa based web browsers (namely Omniweb). Read carefully.

If in System Preferences->International->Language Tab->Languages, you choose a
language other than English which does not use the Roman script (I had Greek) as
the topmost language and English below it, and even if the application itself
does not have a localization for this topmost language (i.e. Chimera not having
a Greek.lproj in this case), Chimera does NOT respond to URL clicks on the
dock/other MacOS X applications. 

Moving English at the top of the list allows for the proper functionality to be
restored.

This has also been found to be a bug in Omniweb, but NOT in IE (Carbon) which
leads me to believe that it is a Cocoa related bug. I have filed it in the
Cocoa-dev list, but I suppose it is useful to you as well.

Regards,

Dimosthenis Kaponis 

Reproducible: Always

Steps to Reproduce:
n/a

Actual Results:  
n/a

Expected Results:  
read above. 

n/a
You might want to submit this bug to Apple as well. Their page is at
http://developer.apple.com/bugreporter/
*** Bug 185960 has been marked as a duplicate of this bug. ***
Solved with Jaguar Update 10.2.3, tested made with Simplified Chinese.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Still does not work with Cyrillic script.
I got the same problem with TeachText before the 10.2.3 update.
Now both Chimera and TeachText can be closed from the Dock.
The only solution is to report it to Apple, no login required.
http://www.apple.com/macosx/feedback/
And perhaps ask on the Apple's Forums, may be someone has a workaround.
You need to log in before you can comment on or make changes to this bug.