API for managing selection state #4

Activity

1. montoya-azul commented on Feb 19, 2015

   

   montoya-azul

   on Feb 19, 2015

   More actions

   Did you solve this?
2. GetContented commented on Jun 14, 2015

   

   GetContented

   on Jun 14, 2015

   More actions

   @spicyj I was also wondering if you'd had any further movement on this. I'm actually just getting it in my normal controlled inpet when typing at a speed over 40 wpm (I happend to have a lot of other stuff going on at the same time in my app).
3. sophiebits commented on Jun 15, 2015

   

   sophiebits

   on Jun 15, 2015

   MemberAuthor

   More actions

   None currently. If you have good ideas we'd love to hear them.
4. syranide commented on Jun 15, 2015

   

   syranide

   on Jun 15, 2015

   More actions

   I did a lot of experiments on this a year or so ago. It's not terribly complex but the API becomes rather cumbersome or inflexible with if done naively:

   A. Always only mutate text left/right/inside of selection, works as-is.
   B. Selection as a property, {text: '', selection: [0, 1]}.
   C. Text left/right/inside of selection as a property, {left: '', right: '', selected: ''}.

   Problem is that only A is self-contained, but it does not behave (strictly) as intended if the value of the input is replaced entirely and is rather inflexible. The other 2 are actually incomplete. So what's really needed is probably a (somewhat) opaque type, provide a bunch of helpers for mutating it.

   Something like this perhaps:

   var FooBar = React.createClass({
     getInitialState() {
       return {
         inputValue: createSuperInputValue({
           value: '',
           onChange: function(value) {}
         })
       }
     },
     mutateInput() {
       this.setState({
         inputValue: fooBarMutateSuperInputValue(this.state.inputValue, ...)
       });
     },
     render() {
       return (
         <SuperInput
           value={this.props.inputValue}
           onChange={newValue => this.setState({inputValue: newValue})}
         />
       );
     }
   });

   However, regardless of what the solution is. Know that in most browsers you end up discarding the undo history, in Chrome you actually end up corrupting it so undoing ruins what you wrote. So my current recommendation is to just stick with text-transform and preventDefault in onKeyPress.