Bug 112554

There's 'shouldEraseMarkersAfterChangeSelection' setting which is exposed to port implementation whether we should erase markers after selection change or not. By default this setting is set on true. Chromium and Mac (at least for wk2) prefer not erasing markers so they return false for this setting. A newly added tests (checked for spelling-double-clicked-word.html) assume that selection (as a result of double click on misspelled word) doesn't erase spelling markers. Here is the code: spellingMarkerRange = internals.markerRangeForNode(textNode, "spelling", 0); <--- OK, marker exists .... // Double-click the misspelled word eventSender.mouseDown(); eventSender.mouseUp(); eventSender.mouseDown(); eventSender.mouseUp(); shouldBeEqualToString("window.getSelection().toString()", "wellcome"); <--- Ok, verifies selection after double click spellingMarkerRange = internals.markerRangeForNode(textNode, "spelling", 0); <--- spellingMarkerRange is NULL for platforms whose erase markers after selection change. I'd like to ask you what's the best way of fixing this issue for other Platforms? It seems reasonably to check whether ports erase markers or not (we could just check spellingMarkerRange object). As a result we will have to deliver new baseline for other ports (at lest EFL). Of course we could implement this behaviour similarly to Chromium and Mac but I am not familiar with it. I couldn't see any visual changes while editing misspelled word in MiniBrowser. Thanks.