ashatora/openlayers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Note about Bing protocol change (see #700)

Browse Source
This commit is contained in:
ahocevar
2012-12-14 01:28:21 +01:00
parent bb788fdd0b
commit ab5035ba05
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
notes/2.13.md
View File

@@ -26,6 +26,14 @@ Corresponding issues/pull requests:
* https://github.com/openlayers/openlayers/pull/484
## Bing Layer
All requests to the Bing Maps service are not sent using the same protocol as the OpenLayers application using the Bing layer. A new config option `protocol` has been introduced to set the protocol to use for requests to the Bing Maps service. For applications hosted on a `file:` url or if in doubt, set `protocol` to 'http:'.
Corresponding issues/pull requests:
* http://github.com/openlayers/openlayers/pull/700
# Behavior Changes from Past Releases
## window.$ is no longer an alias for OpenLayers.Util.getElement
@@ -58,4 +66,4 @@ Corresponding issue/pull requests:
# Different return type for OpenLayers.Format.WMSDescribeLayer
The return type of WMSDescribeLayer format's `read` method was different from the one of the VersionedOGC format superclass. So it was changed from an array to an object with a layerDescriptions property that holds the array. For backwards compatibility, the object still has a length property and 0, ..., n properties with the previous array values.
The return type of WMSDescribeLayer format's `read` method was different from the one of the VersionedOGC format superclass. So it was changed from an array to an object with a layerDescriptions property that holds the array. For backwards compatibility, the object still has a length property and 0, ..., n properties with the previous array values.