Joshua Peek

@github uses https://github.com/josh/rails-behaviors/blob/master/remote_submit.coffee to generically resolve the submit button tracking. I'm a little wary of the complexity of supporting this here.

Sorry, but there is no way to run "blocking" scripts as you can on an initial page load after the fact. Its just not possible with the way DOM fragment...

Its not really possible in CSP 1.0 to feature detect if `eval()` is allowed in a sane way.

It will crash and send back a CSP violation ping back to our servers each time. On Tue, Dec 9, 2014 at 9:51 PM Mislav Marohnić [email protected] wrote: > No?...

Again, that causes a violation report which is unacceptable. On Wed, Dec 10, 2014 at 3:03 AM Leonardo Tietböhl [email protected] wrote: > @josh https://github.com/josh from CSP 1.0 > > If...

I believe rip's env are a replacement rvm's gemsets. I don't think you would use both. But we still need to work out rip's multiple ruby version support in general.

Leaving this to defunkt, but I think the most the docs should be in the manpages. Also, wouldn't want to use the double ## convention. Tomayko has a few conventions...

Would love to deprecate this repository if this feature is upstreamed.

Any chance you could try `master`? Thats currently going to be 3.x, but it has some significant changes around when it checks if the asset is in the precompile list.

Weird, I wonder what is running under `shared/_login_form` thats asset related. Also, what does your `config.assets.precompile` look like? I wonder if theres anything expensive happening there.