Test the correct appearance of the ZoomBox in quirks mode
+
+
+
+
+
For the box to be positioned correctly, we need to know the
+ width of the borders.
+
Shift-click on the map. A red box should be visible around the mouse
+ cursor position, with 20 pixels to the top and right, 10 pixels to
+ the left and 30 pixels to the bottom edge of the box.
+
Drag the box both to the top-left and the bottom-right. The cursor
+ should always be at the top-left or bottom-right inner corner of
+ the box.
Test the correct appearance of the ZoomBox in strict mode
+
+
+
+
+
For the box to be positioned correctly, we need to know the
+ width of the borders.
+
Shift-click on the map. A red box should be visible around the mouse
+ cursor position, with 20 pixels to the top and right, 10 pixels to
+ the left and 30 pixels to the bottom edge of the box.
+
Drag the box both to the top-left and the bottom-right. The cursor
+ should always be at the top-left or bottom-right inner corner of
+ the box.
+
+
+
diff --git a/misc/openlayers/tests/manual/clip-features-svg.html b/misc/openlayers/tests/manual/clip-features-svg.html
new file mode 100644
index 0000000..f4137ea
--- /dev/null
+++ b/misc/openlayers/tests/manual/clip-features-svg.html
@@ -0,0 +1,128 @@
+
+
+SVG inValidRange Test Case
+
+
+
+
+
+
SVG inValidRange Clipping Test Case
+
Behavior before fixing #1631: Push Zoom 5. You see lines. Push
+Zoom 6. No lines.
OpenLayers sketch handlers crossing the dateline example
+
+
+ international date line, dateline, sketch
+
+
+ Start digitizing a polygon or line
+ on one side of the international dateline, and then cross the dateline
+ whilst digitizing. The feature should behave like digitizing on any
+ other location.
+
+ The overlay has an extent smaller than the world extent, but exceeds
+ the world extent. The base layer is configured with wrapDateLine set to
+ true. The area inside the orange rectangle should always contain tiles
+ from the world layer, regardless of the zoom level.
+
+ Draw a few polygons on the map. Some overlapping. Activate the
+ feature handler and ensure that "over" and "out" are called only
+ when mousing over/out of a feature for the first time. The
+ "click" callback should be called for every click on a feature.
+ The "clickout" callback should be called when?
+
+ Tests geodesic measurement of distances and areas against a geodesic ScaleLine.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Zoom in so the ScaleLine shows units in the range of 10-100 km. Measure
+ the length of the ScaleLine. The result should be approximately the same
+ as the distance printed on the ScaleLine.
+
Zoom out so the ScaleLine shows units in the range of 100-500 km. Drag
+ the map to the South or North and see how the ScaleLine length changes.
+
+
diff --git a/misc/openlayers/tests/manual/geojson-geomcoll-reprojection.html b/misc/openlayers/tests/manual/geojson-geomcoll-reprojection.html
new file mode 100644
index 0000000..e82e08a
--- /dev/null
+++ b/misc/openlayers/tests/manual/geojson-geomcoll-reprojection.html
@@ -0,0 +1,74 @@
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/misc/openlayers/tests/manual/google-fullscreen-overlay.html b/misc/openlayers/tests/manual/google-fullscreen-overlay.html
new file mode 100644
index 0000000..80a8fd4
--- /dev/null
+++ b/misc/openlayers/tests/manual/google-fullscreen-overlay.html
@@ -0,0 +1,54 @@
+
+
+
+ Google v3 with Overlay Test
+
+
+
+
+
+
+
+
+
+
Google v3 with Overlay Test
+
+
+
This test shows that the Google layer and overlays are not in sync while dragging or zooming.
+
+
+
+
+
diff --git a/misc/openlayers/tests/manual/google-panning.html b/misc/openlayers/tests/manual/google-panning.html
new file mode 100644
index 0000000..0ccdaf2
--- /dev/null
+++ b/misc/openlayers/tests/manual/google-panning.html
@@ -0,0 +1,122 @@
+
+
+ Google Panning Acceptance Test
+
+
+
+
+
+
+
+
+
+
Even sized map. The map on the left should pan regularly, and the
+ two centers below should be equivalent. Both dragging and panning with
+ buttons should maintain the same center.
+
pixel center:
+ map center:
+ equvalent:
+
+
+
+
+
Odd sized map. The map on the left should pan regularly, and the
+ two centers below should be equivalent. Both dragging and panning with
+ buttons should maintain the same center.
+
pixel center:
+ map center:
+ equvalent:
+
+
+
+
diff --git a/misc/openlayers/tests/manual/google-resize.html b/misc/openlayers/tests/manual/google-resize.html
new file mode 100644
index 0000000..c1384df
--- /dev/null
+++ b/misc/openlayers/tests/manual/google-resize.html
@@ -0,0 +1,55 @@
+
+
+ OpenLayers Google Layer Example
+
+
+
+
+
+
+
+
+
Google Layer Resize Issue
+
+
+
+
+
+
Click
+
+
Open the LayerSwitcher and switch to Google Streets
+
Confirm that the whole map area is populated with tiles
+ OpenLayers uses the disableDefaultUI option of the GMaps API.
+ Despite that, the tilt feature is active. To see it, zoom in
+ once and see the buildings from a 45° angle instead of from the
+ top as you would expect from aerial imagery.
+
+
+
+
+
diff --git a/misc/openlayers/tests/manual/google-v3-resize.html b/misc/openlayers/tests/manual/google-v3-resize.html
new file mode 100644
index 0000000..6949ddc
--- /dev/null
+++ b/misc/openlayers/tests/manual/google-v3-resize.html
@@ -0,0 +1,54 @@
+
+
+ Google v3 Resize Test
+
+
+
+
+
+
+
+
Google Layer Resize Issue
+
+
+
+
+
+
Click
+
+
Open the LayerSwitcher and switch to Google Streets
+
Confirm that the whole map area is populated with tiles
+
+
diff --git a/misc/openlayers/tests/manual/multiple-google-layers.html b/misc/openlayers/tests/manual/multiple-google-layers.html
new file mode 100644
index 0000000..df5c4f0
--- /dev/null
+++ b/misc/openlayers/tests/manual/multiple-google-layers.html
@@ -0,0 +1,135 @@
+
+
+ Multiple Google Layers Acceptance Test
+
+
+
+
+
+
+
+
+
+
+ layers for map1
+
+
+
+
+
+
+
+
+
+
+ layers for map2
+
+
+
+
+
+
+
+
+ This example is used to confirm that resizable maps with multiple
+ Google layers work properly. Click the checkboxes to add/remove
+ layers from the maps. Use the layer switcher to change the map's
+ base layer. You should be able to confirm the following:
+
+
Adding and removing layers doesn't raise any errors
+ (regardless of how many times the same layer is added/removed).
+
The Google "Powered By" link is always visible and clickable
+ when a Google layer is displayed.
+
The Google "Terms of Use" link is always visible and clickable
+ when a Google layer is displayed.
+
Resizing a map (by resizing the browser window) and then
+ changing base layer works well. That is, the center & scale are
+ preserved and all tiles are well aligned.
+
Setting the base layer to the "Dummy Layer" hides all other
+ Google base layers, "Powered By" link, and "Terms of Use" link.
+
+
+
+
+
\ No newline at end of file
diff --git a/misc/openlayers/tests/manual/overviewmap-projection.html b/misc/openlayers/tests/manual/overviewmap-projection.html
new file mode 100644
index 0000000..bb15c9f
--- /dev/null
+++ b/misc/openlayers/tests/manual/overviewmap-projection.html
@@ -0,0 +1,70 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
OpenLayers Overview Map Projection Test
+
+
+
+
+ Acceptance test for different projections in map and overview map.
+ The map uses EPSG:900913, the overview map EPSG:4326. Zoom the map and
+ drag both the map and the overview map to see it in action.
+
+
+
+
+
+
+
+
+
+
diff --git a/misc/openlayers/tests/manual/page-position.html b/misc/openlayers/tests/manual/page-position.html
new file mode 100644
index 0000000..a59dfde
--- /dev/null
+++ b/misc/openlayers/tests/manual/page-position.html
@@ -0,0 +1,103 @@
+
+
+
+ Page Position Test
+
+
+
+
+
+
+
+
+
OpenLayers Page Position Test
+
+
+ Test if borders and scroll position cause unwanted offsets on the
+ mouse positions reported by map events.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
This map's div has a border and absolute positioning, wrapped
+ by a container which also has a border. The page is also
+ scrollable. Neither the borders nor scrolling the page should
+ result in unwanted offsets on pixel positions reported by map
+ events.
+
With the line drawing control active, click on the map to add a
+ point. The point should be drawn at the exact mouse location.
+
With the navigation control active, shift-drag a zoom rectangle.
+ The rectangle's corner should align exactly with the mouse
+ cursor.
Before fixing #1631, after klicking Go! no point would have appeared. The Go! button
+ pans the map over a long distance. Before dragging, the point would have been
+ outside the valid range, and the pan operation would not have triggered the SVG
+ coordinate system to be recreated. The new vector rendering takes care of all this.
+ Click on popup, should be able to read a full sentence, not just two lines.
+
+
+
diff --git a/misc/openlayers/tests/manual/select-feature-right-click.html b/misc/openlayers/tests/manual/select-feature-right-click.html
new file mode 100644
index 0000000..edd79d6
--- /dev/null
+++ b/misc/openlayers/tests/manual/select-feature-right-click.html
@@ -0,0 +1,86 @@
+
+
+ OpenLayers Ticket 3404
+
+
+
+
This bug is only triggered by physical right mouse clicks so it is not possible to write
+ an automated js unit test
+
When a SelectFeature control and a Navigation control are added to a map the left-click
+ mousedown events are stopped by a Drag handler before reaching the Feature handler. However,
+ right-click mousedown events so pass through and reach the Feature handler.
+
The Feature handler records the xy of
+ each mousedown and mouseup events so they can be compared in the click event. Because only right-click
+ mousedown event are received the location of future left-click mouseup events are compared
+ to the location of the 'stale' right-click mousedown event resulting in the feature not being selected.
+
Steps to recreate the bug:
+
+
Left-click a point to select it.
+
Left-click the map to deselect the point.
+
Left-click a different point to select it.
+
Left-click the map to deselect the second point.
+
Right-click the map then left-click to close the browser context menu.
+
+ The map includes two select feature controls. The first one operates on
+ geometries of type OpenLayers.Geometry.Point only and works on clicks. The
+ second one operates on geometries of type OpenLayers.Geometry.Polygon and
+ works on mouseover's. If you select the point geometry by clicking on it,
+ it shouldn't be unselected when the mouse moves out if it.
+
+
+
+ Test 0 : at the initial zoom the WMS layer is in range, you should
+ therefore see the 'Loading tiles...' message when loading the page for
+ the first time.
+
+
+
+
+ Test 1 : If you zoom out by one level (using the zoombar), the WMS
+ layer becomes out of range. No tile should be loaded so you shouldn't see
+ the 'Loading tiles...' message.
+
+
+
+
+ Test 2 : Zoom in by one level to go back to initial state (the WMS
+ is back). Open the layer switcher and turn off the WMS layer. No tile
+ should be loaded so you shouldn't see the 'Loading tiles...' message.
+
+
+
+
+ Test 3 : Keep the WMS layer turned off in the layer switcher. Zoom
+ out by one level again. The layer is both invisible and out of range, so
+ you shouldn't see the 'Loading tiles...' message.
+
+
+
WMS Layer state - in range: true, visibility: true
+
+
\ No newline at end of file
diff --git a/misc/openlayers/tests/manual/vector-features-performance.html b/misc/openlayers/tests/manual/vector-features-performance.html
new file mode 100644
index 0000000..7990379
--- /dev/null
+++ b/misc/openlayers/tests/manual/vector-features-performance.html
@@ -0,0 +1,149 @@
+
+
+ Vector Features Performance Test
+
+
+
+
+
+
+
+
New Rendering - Vector Features Performance Test
+
+
+ This test examines if checking for a feature being inside the visible
+ extent before rendering it has an impact on performance. Open the Firebug
+ console after running this test (hit F12) to see the results.
+
+ After the performance test, you can drag around the map to see how the new
+ vector rendering feels where features get rendered only when they are visible
+ inside the map extent.
+
+
+ The map includes one base layer (vmap0) and three overlays, namely a vector
+ layer, a fake layer with no images, and a dmsolutions layer. The overlays are
+ added to the map in this order: the vector layer, the fake layer, and the
+ dmsolutions layer. The map also includes a select feature control, which
+ when activated bumped the vector layer z-index to some high value. This
+ makes feature selection work, even though other overlays were added after
+ the vector layer.
+
+
+
+
+ If the fake layer is removed from the map (first link below), the vector layer's
+ z-index must not be reset, so the vector layer must not go under the
+ dmsolutions layer and feature selection must continue to function as
+ expected.
+
+
+
+
+ If one of the SelectFeature controls is deactivated or activated (second
+ and third link below), the vector layer should change it's position in the
+ layer stack: on top if at least one of the controls is activated, covered
+ by other layers if both are deactivated.
+
+