Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling SCAYT breaks anchor text #39

Open
adelura opened this issue Mar 31, 2014 · 3 comments
Open

Enabling SCAYT breaks anchor text #39

adelura opened this issue Mar 31, 2014 · 3 comments

Comments

@adelura
Copy link

adelura commented Mar 31, 2014

Tested and confirmed in CKEditor 4.3.3 and 4.4.0 (prerelease)
Browsers: all

  1. Load the following content in editor

    <p><a name="anchor1">anchor mis</a>pell</p>
    
  2. Wait until word "mispell" is marked by SCAYT

    • Actual Result: marker splits up the anchor into two, with each of them get applies the anchor styles.
  3. Click "source button" to get into source mode

  4. Click "source button" to get into editor mode

    • Actual Result: creates new anchors

Original bug reported at: http://dev.ckeditor.com/ticket/7812

@Reinmar
Copy link
Contributor

Reinmar commented Apr 12, 2014

Another TC:

  • Load <p>Foo <a href="x">http://foofoofoo</a> bar</p>.
  • Enable SCAYT.
  • Switch to source mode.
  • Result: everything is ok.

However:

  • Load <p>Foo<a href="x">http://foofoofoo</a> bar</p>.
  • Enable SCAYT.
  • Switch to source mode.
  • Result: link has been split.

@WebSpellChecker
Copy link
Collaborator

The problem is confirmed. Thanks for the detailed TCs. The issue was added to our Backlog with normal priority. We'll update the status of ticket as soon as we start working on the fix.

@jshaptala
Copy link
Member

Hello, this is to inform you that at the moment the issue has not been fixed yet, however, you may fix this problem on your side by disabling SCAYT for specific elements using the next parameter: scayt_elementsToIgnore

Like here: "config.scayt_elementsToIgnore = 'a';"

At the moment we do not have an ETA when it will be fixed as it resides on our back log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants