Elementpath work with SCAYT

[Garry Yao]

Elementpath should hide SCAYT marker '<span>' from end user.

[WebSpellChecker.net]

patch is submitted in #5145

[Frederico Caldeira Knabben]

It's ok to indicate that this one is supposed to be fixed by another tickets, but it should be closed only after confirming the fix one the relative ticket gets closed.

[Frederico Caldeira Knabben]

Maybe it's better to have a generic solution for it, like having a standard attribute to be appended to elements to be ignored in the elements path.

[Garry Yao]

Introduce a generic config option for achieving that.

[WebSpellChecker.net]

Here is idea. Does it make a sence to add some method to the Elementpath which allow to register set of keys which should be taken into account when Elementpath works. There should be ability to unregister this set of keys. This method can be called from plug-ins.

Ignore(
{/*String*/ param1: /*String*/value1,
 /*String*/ param2: /*String*/value2,
 ...
}

where

paramX - property name | attribute name valueX - value or part of value which paramX may contain or null which means that paramX should be checked for existance

Samples:

Ignore(
{
  "scaytid": null
});

or

Ignore(
{
  "nodeName": "span",
  "class": "ignore"
});

or

if on the page <b> is suppressed by the style:

b { font-weight: normal }

and only <strong> should be displayed then Ignore method can be called following way:

Ignore(
{
  "nodeName": "b"
});

[Garry Yao]

The provided patch could achieve that: config.elementsPath_filters.push( function( element ) {

if( element.is( 'b' ) && element.getComputedStyle( 'font-weight' ) == 'normal' ) )

return false;

});

[Alfonso Martínez de Lizarrondo]

In the documentation it's written once 'myAttribue', just fix that before committing.

[Garry Yao]

Fixed with [5228].