[Cartoweb-users] Cartoweb and Firefox 3

[Chris Duncan, GISmatters]

Could someone please clarify what is meant by:

"the patch"

and

"set a new property for the #map.layer class"?

I'm just going live with a new Cartoweb application and would like to 
ensure that it is compatible with FF3, but the thread quoted below 
isn't clear to me. Is there a "patch" that is separate from "setting a 
new property"? Or is "setting a new property" the actual patch? In any 
case, what new property needs to be set? Just make up a random dummy 
property?

If someone has the time to provide a simple, specific step-by-step, 
I'd appreciate it.

Thanks,

Chris


Bruno Friedmann wrote:
> Hi Pierre,
> 
> I've just try the patch. Work great here ( FF3 under linux )
> I've not access to a ff3 win32 install now. But think It should work also.
> 
> Nice quick & dirty catch. A prototype update would be nice also, no ?
> 
> 
> Pierre GIRAUD wrote:
>> Hello all,
>>
>> I was asked to have a look at this problem with FF3 and I think I found
>> a solution.
>> The "workaround" is to set a new property for the #map.layer class in
>> dhtml.css as described in the patch.
>>
>> Right now, I'm looking for a response from the bugzilla server which
>> seems to be down currently.
>>
>> However, I would be happy if you let me know if this works.
>>
>> Regards,
>> Pierre
>>
>> Oliver Christen wrote:
>>> mmm, the dhtml do not seems to use prototype's getElementsByClassName,
>>> it use xGetElementsByClassName which doesnt redefine the core
>>> getElementsByClassName function.
>>>
>>> but since the problem you noticed happens only in ajax mode, it also
>>> means the problem happens only prototye.js is loaded so it is linked
>>> somehow. We will look into that.
>>>
>>> thank you
>>>
>>> regards
>>> Oliver
>>>
>>>
>>>
>>>> I think the real trouble are located in the regression prototype.js
>>>>
>>>> http://ejohn.org/blog/getelementsbyclassname-pre-prototype-16/
>>>>
>>>> (don't have time today to look at it )
>>>> But I know that cw3 use quiet very old version ( 1.5rc )
>>>>
>>>> This should also have impact on dhtml.js an certainly quiet a lot's
>>>> of code inside cw3
>>>> (I really hope that's not the case :-) )))
>>>>
>>>> Tell us if your analyse drive you to the same index.
>>>>
>>>> Oliver Christen wrote:
>>>>> Hi
>>>>>
>>>>> thank you for reporting this.
>>>>> the problem occure specificaly when ajax is enabled.
>>>>> all clic-drag tools are effectively affected.
>>>>> we are currently looking into this matter.
>>>>>
>>>>> regards
>>>>> Oliver
>>>>>
>>>>>
>>>>>> Kurt Menke wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I've noticed that the Cartoweb zoom functionality, and the client in
>>>>>>> general, hangs a lot more often in Firefox 3.  I have to use the
>>>>>>> Refresh
>>>>>>> button a lot.  For instance, I can use the zoom tool once fine and
>>>>>>> the
>>>>>>> second time it doesn't zoom to the correct area unless I Refresh.  It
>>>>>>> worked
>>>>>>> beautifully in Firefox 2.  Has anyone looked into this?
>>>>>>>
>>>>>>> Kurt
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> **************************
>>>>>>>
>>>>>> Absolutely +1. We seen exactly the same trouble.
>>>>>> Other tools that need point,clic and drag have the same trouble
>>>>>> (outline,measure...)
>>>>>>
>>>>>> -- 
> 
> 

-- 

Chris Duncan, Ph.D.
President
GISmatters

duncan at GISmatters.com
http://www.gismatters.com/

1 Tuckerman Ln
Amherst, MA 01002

Tel: 413-549-2052
Fax: 508-637-2557