crschmidt ba5b664a2f Firefox SVG does not support drawing points with values more than something ...

between 10,000 and 40,000. (It's hard to tell, since it crashes the browser 
when you try.) The resulting behavior is that the browser crashes. This 
wraps these values into Pixel regions, and doesn't draw features which fall 
outside of them. (This sucks, but the result is the browser not crashing.) 
This closes #669, and should be improved as described in #670 for 2.5.

If for some reason you know that the browser you're on can support larger 
maxPixel values, you can adjust the maxPixel private variable on the 
renderer. I believe that Opera and WebKit nightlies will work fine with 
a larger maxPixel value. Changing this is encouraged *only* if you 
are developer working on the code, because it can totally crash browsers 
in a production environment.


git-svn-id: http://svn.openlayers.org/trunk/openlayers@3071 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf

2007-04-13 12:40:22 +00:00

..

Elements.js

#655: add layer.eraseFeatures.patch() on the "public" side of the API - layer methods should be called instead of layer.renderer methods wherever possible

2007-04-11 15:48:41 +00:00

SVG.js

Firefox SVG does not support drawing points with values more than something

2007-04-13 12:40:22 +00:00

VML.js

#628 - a feature has a geometry - a geometry doesn't have a feature - features are rendered, selected, moved, modified, etc - down in the renderer, expando properties on nodes are limited to _featureId, _style, and _options - this removes expandos that created circular references back through the map and to other dom elements - when the renderer is involved in selecting features, it returns a featureId (instead of a geometry or feature) and the layer is responsible for fetching the appropriate feature

2007-04-10 16:07:56 +00:00