[OpenLayers-Users] OL 2.11 possible Bug with Chrome
Ricardo Bayley
ricardo.bayley at gmail.com
Tue Jun 7 14:32:07 EDT 2011
I agree with Chris.
although I would like to better explain what happened.
setting *OpenLayers.Layer.Vector.prototype.renderers = ["SVG2", "VML",
"Canvas"];*
worked well with chrome but it caused issues (duplicity) with OL2.10. I
guess this is normal, since this is only for OL2.11
The problem I faced having set the renderer using OL2.11 is that the
SelectFeature
control wont work in all features.
Hope it helps,
Ricardo
2011/6/7 <christopher.schmidt at nokia.com>
>
> On Jun 7, 2011, at 12:08 PM, ext Eric Lemoine wrote:
>
> > On Tue, Jun 7, 2011 at 5:18 PM, <christopher.schmidt at nokia.com> wrote:
> >> This is using the new SVG2 renderer, which is intended to provide better
> performance.
> >> Perhaps this renderer isn't perfectly suited for Chrome at the moment;
> using the
> >> existing SVG renderer will use the code we've been using for a lot
> longer, and may be
> >> safer for the time being.
> >
> > Yet, shouldn't we fix that for 2.11? I don't feel comfortable with
> > shipping new features with major bugs like this.
>
> It's not a regression. We're specifically shipping that functionality so
> that
> people can do like this person did: enable it, test it, and report issues.
>
> If this is an easy fix, and someone cooks up a patch, I'm not against
> pulling
> it up (since it's low risk: no one will be using the code by default),
> but I don't think it's a release blocker.
>
> -- Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/openlayers-users/attachments/20110607/09f05c5c/attachment.html
More information about the Users
mailing list