generate both Id and Name for anchors

[Alfonso Martínez de Lizarrondo]

Currently the anchors do create just <a name=""> but, if also an id is automatically generated, then it can help to do dynamical effects on the page (for example clicking on a link and smoothly scroll to the anchor pointed by the link)

Some people even state that only IDs should be generated as names are just something from the past, but that's another battle.

[richsky]

I was close to create a new ticket. But I think this it important. As soon as you have an HTML page with anchor identified by ids and not by "name", they don't appear.

I would like the anchor to be available and editable by "ids".

[Anna Tomanek]

I second this request.

Please note that ​HTML5 will only support "id" for an <a> element. Moreover, when ​scrolling to a fragment identifier HTML5 will first look for an element with a given "id" and only then try to find the <a> element with a matching "name" attribute.

[Fabian Vogelsteller]

i would like to see this feature too.. adding both name and id.

[Loren]

Patch attached

[Jakub Ś]

@wiseloren field version is used to indicate when problem first occurred. Please don't change it.

[Loren]

Sorry about that good to know. I was thinking it would be the version the patch was made for.

[Frederico Caldeira Knabben]

Fixed with [7618].

[sean]

I'd like to report that having BOTH name and id breaks PHP's DOMDocument::loadHTML().

The answer here explains that: ​http://stackoverflow.com/questions/3614586/dom-error-id-someanchor-already-defined-in-entity-line

I've made my own link plugin that patch reverted, which works well.

[Jakub Ś]

But this is allowed in HTML. Even Link you have given says that HTML spec. allows it. There is o error in HTML and CKEditor but in PHP.