[Laszlo-dev] [RESENT] Re: supporting XULrunner as a browser for DHTML

[P T Withington]

[Resent to Laszlo-Dev]

The checking is in our default, auto-generated wrapper page (via our  
default embedding code), not in the app.  And I thought max made it  
use a cookie so you could say "don't ask" just once?

The simplest thing for [the customer] to do is to create their own  
wrapper page and call dhtmlEmbedLFC with a second argument  
(allowUnsupported) of `true`, which turns off the check.

On 2008-04-17, at 12:52 EDT, David Temkin wrote:
> I have a suggestion:
>
> Let's remove the browser checking code altogether -- or leave it in  
> the OL distro as a separate utility, but separate it out from  
> compiled apps.
>
> I have had the experience of running OL/DHTML apps in "unsupported"  
> browsers which in fact do work. My preference is to just get rid of  
> the compat. check, and leave it up to the application (really, the  
> HTML that wraps the application) to do whatever checks, if any, that  
> it wants to do.
>
> - D.
>
>
>
> On Apr 17, 2008, at 9:10 AM, Henry Minsky wrote:
>
>> [the customer] has a bug where the version of Firefox they are  
>> using embedded into their IDE, XULrunner, gets flagged as
>> a non-supported runtime by our browser checking code.
>>
>> [the customer] says:"
>>
>> you most likely test that string : Mozilla/5.0 (Windows; U; Windows  
>> NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 and  
>> check for " Firefox/2.0.0.13" whne in fact the GRE version is the  
>> important one "rv:1.8.1.13"
>>
>> Where would I go to modify the check to allow XULrunner ?