OpenLayers OpenLayers

Ticket #1102 (closed bug: duplicate)

Opened 1 year ago

Last modified 4 months ago

margin on html element messes with mouse position

Reported by: tschaub Assigned to:
Priority: minor Milestone: 2.7 Release
Component: general Version: 2.5
Keywords: Cc:
State:

Description

Given a map on a page with non-zero margin, editing tools show messed up mouse position.

Change History

10/22/07 19:19:15 changed by tschaub

html {margin: 1em;}

10/22/07 19:23:44 changed by crschmidt

Index: lib/OpenLayers/Util.js =================================================================== --- lib/OpenLayers/Util.js (revision 4989) +++ lib/OpenLayers/Util.js (working copy) @@ -990,7 +990,7 @@

var child = forElement; while(element) {

- if(element == document.body) { + if(element == document.body.parentNode) {

// FIXME: IE, when passed 'window' as the forElement, treats it as // equal to document.body, but window.style fails, so getStyle // fails, so we are paranoid and check this here. This check should

10/22/07 19:23:55 changed by crschmidt 

Index: lib/OpenLayers/Util.js
===================================================================
--- lib/OpenLayers/Util.js      (revision 4989)
+++ lib/OpenLayers/Util.js      (working copy)
@@ -990,7 +990,7 @@
     var child = forElement;
     while(element) {
 
-        if(element == document.body) {
+        if(element == document.body.parentNode) {
             // FIXME: IE, when passed 'window' as the forElement, treats it as
             // equal to document.body, but window.style fails, so getStyle
             // fails, so we are paranoid and check this here. This check should

01/16/08 10:07:20 changed by crschmidt

  • state changed.
  • summary changed from margin messes with mouse position to margin on html element messes with mouse position.

01/22/08 17:41:58 changed by crschmidt

  • milestone changed from 2.6 Release to 2.7 Release.

Mass ticket move to 2.7 post dev meeting. If you are actively working on this task, please update this ticket with information and change the milestone to 2.6. At the time of the next IRC meeting (most likely 1-31-08), this will mean the ticket can *not* be brought back into 2.6 unless there is further feedback.

07/02/08 03:36:57 changed by euzuro

this might be at least loosely related to #1051

07/28/08 12:59:42 changed by crschmidt

  • status changed from new to closed.
  • resolution set to duplicate.

#1179