Ticket #1368 (closed bug: duplicate)

Opened 5 years ago

Last modified 4 years ago

Editing OL.Layer.Vector in IE selects DOM-element, causing "blue overlay" flicker on map

Reported by: bjorn Owned by:
Priority: minor Milestone: 2.8 Release
Component: Renderer Version: SVN
Keywords: VML Cc:
State:

Description

When editing features in IE the browser sometimes picks this up as element selection of the whole OL div (I think). This toggles back and forth causing the map to flicker with opague blue background. This happens most frequently when dragging lines or polygon vertices.

I have investigated the issue and found that the flickering is introduced in r5772. However I still think element selecion occurs in earlier revs, since there is noticable rendering speed hickups coinciding with the flickering in r5772 whereas in r5771 there is only the hickups.

I have only verfied this with IE7 at the moment, but think it affects IE6 too.

Change History

Changed 5 years ago by bjorn

  • keywords VML added
  • component changed from general to Renderer
  • milestone set to 2.6 Release

Changed 5 years ago by bjorn

  • summary changed from Editing OL.Layer.Vector in IE causes element selection to Editing OL.Layer.Vector in IE selects DOM-element, causing "blue overlay" flicker on map

Changed 5 years ago by crschmidt

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

Duped by #1410

Changed 4 years ago by bjornharrtell

  • status changed from closed to reopened
  • resolution duplicate deleted
  • milestone changed from 2.6 Release to 2.8 Release

I'm sorry to say that after some investigation this problem seem to be back. Noticed performance hickups after testing IE8 with recent trunk versions - thought it was IE8 but I have now tested with IE6 and IE7 too and the crap is back :(

I do not have this problem in 2.7 and I think there is no issues with selection, just the same performance problem as described in this ticket. I will as soon as possible try to find which revision between 2.7 and trunk which regressed this.

Changed 4 years ago by bjornharrtell

Actually I don't remember if fixing the selection-stuff fixed the performance problem last time, but something did way back - it definitely was there - and now it's back for some reason :(

Changed 4 years ago by bjornharrtell

  • status changed from reopened to closed
  • resolution set to duplicate
Note: See TracTickets for help on using tickets.