I agree with Chris. <div><br></div><div>although I would like to better explain what happened.</div><div>setting <span class="Apple-style-span" style="border-collapse: collapse; color: rgb(102, 0, 0); font-family: arial, sans-serif; font-size: 13px; "><b>OpenLayers.Layer.Vector.prototype.renderers = ["SVG2", "VML", "Canvas"];</b></span><br>
worked well with chrome but it caused issues (duplicity) with OL2.10. I guess this is normal, since this is only for OL2.11</div><div><br></div><div>The problem I faced having set the renderer using OL2.11 is that the <span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">SelectFeature control wont work in all features.</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Hope it helps,</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Ricardo</span></font></div><div><br></div><div><br><div class="gmail_quote">
2011/6/7 <span dir="ltr"><<a href="mailto:christopher.schmidt@nokia.com">christopher.schmidt@nokia.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On Jun 7, 2011, at 12:08 PM, ext Eric Lemoine wrote:<br>
<br>
> On Tue, Jun 7, 2011 at 5:18 PM, <<a href="mailto:christopher.schmidt@nokia.com">christopher.schmidt@nokia.com</a>> wrote:<br>
>> This is using the new SVG2 renderer, which is intended to provide better performance.<br>
>> Perhaps this renderer isn't perfectly suited for Chrome at the moment; using the<br>
>> existing SVG renderer will use the code we've been using for a lot longer, and may be<br>
>> safer for the time being.<br>
><br>
> Yet, shouldn't we fix that for 2.11? I don't feel comfortable with<br>
> shipping new features with major bugs like this.<br>
<br>
</div>It's not a regression. We're specifically shipping that functionality so that<br>
people can do like this person did: enable it, test it, and report issues.<br>
<br>
If this is an easy fix, and someone cooks up a patch, I'm not against pulling<br>
it up (since it's low risk: no one will be using the code by default),<br>
but I don't think it's a release blocker.<br>
<br>
-- Chris</blockquote></div><br></div>