> Hi Peter,

Hi Daniel,


> we try to avoid browser/engine checks whenever possible, especially in 
> the environment detection classes, because they're fairly unreliable. 

Yeah I know. And that's something I don't want to maintain myself, therefore I
am very thankful ;)


> For example, IE 11 Preview no longer includes "IE" in its user agent 
> string, identifying itself as a Gecko-engined browser instead (even 
> though some Gecko-specific code will break it...). So relying on feature
> detection, even if it means lots of try/catch blocks, is a good way to 
> future-proof the framework.
> 
> Besides, there are several other environment checks in qx.bom.client 
> that also throw and catch exceptions where we couldn't use an engine 
> switch even if we wanted to because it's not as straightforward as it is 
> with ActiveX.

But non of them bothered me anytime. And many other try/catch blocks are
governed by other checks (e.g. in Plugin.__getVersion) so I thought one
further check might not be a problem.
Even more because the qooxdoo Environment class promised to deliver reliable
informations, right?

Also e.g. qx.bom.client.Engine.getName() == "mshtml" should be true in _every_
IE, but isn't. Shouldn't there be _one_ defined Method that returns a defined
value (e.g. "ie") for _every_ IE browser?
I see that qx.bom.client.Browser.getName() on 'mshtml'-engine can return
either "ie", "iemobile" or whatever the lowercase-regular-expression returned.
I am not able to pick the right call for getting the environment right ;)

Anyway, engine-specifics are not an easy task, but I am still annoyed that
firebug hits that damn try/catch-block every time :(


> Regards,
> Daniel

Thanks for the response and any work so far,
  Peter


> On 09.10.2013 17:11, Peter Schneider wrote:
>> Hi there,
>>
>> I was wondering why the check at qx.bom.client.Plugin.getActiveX() does not
>> check for "mshtml" engine?
>>
>> The problem is, I am running on firefox with firebug and enable the
>> "stop on all errors" option at the "Console" Tab.
>> That -although caught- exception (see below) triggers a halt.
>>
>> Although I can deactivate that specific halt by deactivating it once it
>> appeared, but what I really would like is that this does not happen at all.
>>
>> Couldn't the check (in the try block if getActiveX) include a check for IE?
>> Like:
>> <code>
>> return qx.core.Environment.get("engine.name") == "mshtml" &&
>>    (typeof (new window.ActiveXObject("Microsoft.XMLHTTP")) === "object" ||
>>      typeof (new window.ActiveXObject("MSXML2.DOMDocument.6.0")) === 
>> "object");
>> <code>
>>
>> ...instead of the current:
>>
>> <code>
>> return (typeof (new window.ActiveXObject("Microsoft.XMLHTTP")) === "object" 
>> ||
>>       typeof (new window.ActiveXObject("MSXML2.DOMDocument.6.0")) === 
>> "object");
>> <code>
>>
>> Or is "window.ActiveXObject" present/available/usable in any other client?
>>
>> See bug 7498[1] for further details.
>>
>> Regards & thanks in advance,
>>    Peter
>>
>>
>> [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=7498

-- 

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to