This project is read-only.


Playground features severly limited with Opera


Neither type tooltips nor completion seem to work with Opera (12.02, Windows 7). Completion after dot starts, then hangs.

With Opera as my default browser, I wasn't aware of these features until they were mentioned in a discussion!-) Which is a pity, given that these tools are somewhat central to Typescript's goals.
Closed Feb 26, 2013 at 12:16 AM by RyanCavanaugh
Might have been some Azure problems we were having -- please re-open if you're seeing this lately. Thanks!


LukeH wrote Oct 25, 2012 at 7:18 PM

I see both completion lists and tooltips working for me on Opera 12.02 1578 on Windows 8. Do you see the lack of these consistently? Do you have a different build of Opera?

clausreinke wrote Oct 25, 2012 at 8:30 PM

Strange, I have the same build. And, yes, the lack is consistent, even on minimal examples (eg, 'console.log'). On loading the playground, Opera's error console shows

[25.10.2012 21:22:43] JavaScript -
Web Worker exception
Syntax error processing script

but I don't see a way to pin this down (another argument for having the playground source in the repo?-).

clausreinke wrote Oct 29, 2012 at 10:53 PM

I have now been able to see both features by using a second Opera instance, with a fresh profile.

Still no luck with my main instance and default profile - I've given your site all permissions, cleared all caches, cookies and persistent storage, restarted the browser, disabled caching in dragonfly.

I was hoping for a caching header issue, but chances are increasing that this is an Opera or local settings issue. If it wasn't for the site not working, I'd say the settings are no longer
different in the two Opera profiles..

From comparing the network protocols, there should be some workerservers loading that do not appear in the faulty sessions. If I had unminified code, I would try to instrument the web workers, but without that, I don't see how to pursue this further. If other Opera users are not affected, you might want to close the issue.

clausreinke wrote Feb 26, 2013 at 10:00 PM

I'm still seeing this with my main opera instance but suspect its some local profile issue (with opera not telling me which profile entry is causing its webworkers to fail on the site, though it could be related to the many non-standard tricks on the site). So I won't reopen unless I can confirm otherwise.

Btw, your playground team should look at mobile browsers, too. On my Nexus 7, none of the browsers I tried (chrome, opera mobile) could successfully use the playground.