Currently Being ModeratedFeb 4, 2013 8:38 AM (in response to till213)
It is not only File:// and then abc behind it. Also File:// with a third / behind it. It is a known phenomenon in Mountain Lion, Apple is aware of it.
There are more threads here. If you want to search for it type a space between the slashes otherwise your application will crash.
Currently Being ModeratedFeb 4, 2013 9:01 AM (in response to LexSchellings)
As Lex says, it is a well documented, obscure bug. Apple is aware of it and working on a fix.
It's unlikely you'll ever see it unless you decide to try this at home.
Do not try this at home!!!
Or at work... or anywhere.
Currently Being ModeratedFeb 4, 2013 2:32 PM (in response to LexSchellings)
> If you want to search for it type a space between the slashes otherwise your application will crash.
Nope. Running Firefox on 10.6.8. All smooth and fine here ;)
By the way: is Xcode also affected? I'm trying to imagine that poor fella who's supposed to write the unit-test for that one ;) (And Apple does "test first" development, right? Right? ;))
Currently Being ModeratedFeb 4, 2013 2:52 PM (in response to till213)
I think any app that has the default text view and supports data detectors will exhibit this problem. So Xcode may be affected.
How common it is to type that as File: followed by 3 slashes with a capital F seems the issue. Can absolutely every combination on earth be tested? I mean, now that word is out it's easily to replicate it, but if the problem has been around for many months and was only found by someone now, it must mean it's not very common to see, given there are tens of millions of people using the OS every day. URL conventions are all lower case so I'd say the workaround for now is just to type the file URL properly if you want to use it ;-)