Ray Cohen

Making `push` behavior the default doesn't seem to line up with what we do most often. I like the different API for each case idea.

thumbs up On Fri, Jan 2, 2015 at 5:28 PM, Stefan Penner [email protected] wrote: > @raycohen https://github.com/raycohen maybe we leave becomeKeyResponder > - deprecate, but then add pushKeyResponder and replaceKeyResponder...

We don't currently have a good way to support `data-test` attributes directly on the input element. I would recommend putting a data-test attribute on an ancestor and then using something...

would we be providing things like `KeyUpCtrlAltShiftE` ?

is there a performance difference between the two approaches? What about supplying methods to help match: ``` import keyMatcher from 'ember-key-responder/key-matcher'; handleKey: function(e) { if (keyMatcher.test(e, 'b')) { // b...

I've observed the same bug pointing my android chrome or android firefox browser to http://bustle.github.io/mobiledoc-kit/demo/ as well as in our app. Its severe enough to make it borderline unusable. Any...

@bantic Yes, that screengrab matches the behavior I get in Chrome on a Pixel 2. Firefox on android is definitely less important to us, but it has an additional quirk...

a config file that allows you to control all of the CLI flags would be nice. the package.json script line gets really long if you toggle a few things. also,...

This is fixed in 3.0.0-beta.1 via https://github.com/yapplabs/ember-radio-button/pull/141

I am trying to convert a legacy addon into a v2 addon in a project using ember-auto-import and I think I am running into this as well