Bug 515212 - Make the generic text editor the new default instead of the old text editor
Summary: Make the generic text editor the new default instead of the old text editor
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-12 14:10 EDT by Lars Vogel CLA
Modified: 2017-04-13 11:14 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2017-04-12 14:10:24 EDT
Bug 497871 provided an extensible text editor. I suggest to make it the new default.
Comment 1 Dani Megert CLA 2017-04-13 06:28:51 EDT
-1 for that, but I'm fine to hook it to those content types for which we already have an extension for the generic editor.
Comment 2 Alexander Kurtakov CLA 2017-04-13 06:57:07 EDT
(In reply to Dani Megert from comment #1)
> -1 for that, but I'm fine to hook it to those content types for which we
> already have an extension for the generic editor.

Dani, would you explain why? There are things like the word completion which makes for way better user experience in cases where there is no specialized editor.
Comment 3 Dani Megert CLA 2017-04-13 09:59:20 EDT
(In reply to Alexander Kurtakov from comment #2)
> (In reply to Dani Megert from comment #1)
> > -1 for that, but I'm fine to hook it to those content types for which we
> > already have an extension for the generic editor.
> 
> Dani, would you explain why?

The standard text editor should be the simple text editor that has no side-effects.


> There are things like the word completion which
> makes for way better user experience in cases where there is no specialized
> editor.

Can you explain what you mean? To my knowledge the Text Editor has spell checking enabled by default, allowing to use Ctrl+1 to fix/complete words. This is not the case with the Generic Editor.
Comment 4 Alexander Kurtakov CLA 2017-04-13 11:07:48 EDT
(In reply to Dani Megert from comment #3)
> (In reply to Alexander Kurtakov from comment #2)
> > (In reply to Dani Megert from comment #1)
> > > -1 for that, but I'm fine to hook it to those content types for which we
> > > already have an extension for the generic editor.
> > 
> > Dani, would you explain why?
> 
> The standard text editor should be the simple text editor that has no
> side-effects.
> 
> 
> > There are things like the word completion which
> > makes for way better user experience in cases where there is no specialized
> > editor.
> 
> Can you explain what you mean? To my knowledge the Text Editor has spell
> checking enabled by default, allowing to use Ctrl+1 to fix/complete words.
> This is not the case with the Generic Editor.

See bug 514397 for details for word completion. If spell checking is the deal breaker, it can be added to generic editor too.
Comment 5 Dani Megert CLA 2017-04-13 11:14:14 EDT
(In reply to Alexander Kurtakov from comment #4)
> If spell checking is the
> deal breaker, it can be added to generic editor too.

See bug 513314. There *is* a difference between a simple text editor and a more powerful one.