Are 2SCM attributes a new kind of attributes?

[jodator]

After working with @pomek on various improvements on typing around link I came to a conclusion that code could (should) behave the same way as link:

• Removing text after code should also result in not typing with code (After backspacing into a link, the caret should still stay outside #7521).
• Typing over code could also result in replacing the code inside (Typing over the link (replacing link text) #4762).
• What should happen when content is delete around link and code (What should removing the text around link do. #7676)?

ATM we have only two 2SCM features that could potentially behave in a similar fashion. As @pomek noticed we fix how text attributes interact with selection for link:

• we want to type with bold but not with link, 
• we have 2SCM for link not bold,
• etc

To make link act differently then bold we introduced "hacks" or overrides to a default editor behavior. Which is fine for one feature. However, if we decide that code should behave the same way as link then I think that we might introduce a "non-sticky" attribute.

I don't have a valid RFC for this - so this is an invitation to discuss some things first.

• do we want to code behave the same way as linkHref
• do we see then a need for a new attribute's property?

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.

[Reinmar]

• do we want to code behave the same way as linkHref

I started wondering about this as well recently. And I don't have an opinion here yet. Let's use this for a while in GitHub Writer.

• do we see then a need for a new attribute's property?

Potentially. I don't know how hacky the implementation is in the end and whether it can be actually simplified if that landed in the engine.

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

We've closed your issue due to inactivity over the last year. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).