The current implementation of "Edit" on an experience fragment component adds the Pencil icon to the component's edit menu after the Parent icon. Authors are accustomed to the "Edit" pencil being the first icon in the list, prior to the Wrench icon. This is how Content Fragment is implemented, which leverages the OOTB capability to register inline editing for a component.
The changes would be as follows:
Add the localizedFragmentVariationPath to an HTML attribute
Update the editor hook JS to code very similar to the Content Fragment editor hook, using Granite.author.editor.register to register the edit action
Update cq:editConfig of Experience Fragment to add the cq:inplaceEditing node referencing the editorType registered in the JS
Update cq:editConfig of Experience fragment to remove the cq:actionConfigs that is registering the "custom" editInNewTab action.
The current implementation of "Edit" on an experience fragment component adds the Pencil icon to the component's edit menu after the
Parenticon. Authors are accustomed to the "Edit" pencil being the first icon in the list, prior to the Wrench icon. This is how Content Fragment is implemented, which leverages the OOTB capability to register inline editing for a component.The changes would be as follows:
localizedFragmentVariationPathto an HTML attributeGranite.author.editor.registerto register the edit actioncq:editConfigof Experience Fragment to add thecq:inplaceEditingnode referencing theeditorTyperegistered in the JScq:editConfigof Experience fragment to remove thecq:actionConfigsthat is registering the "custom"editInNewTabaction.