Currently I'm investigate yet another issues also related to assets
pipeline that are still affecting me and I still don't have a work-around.
For some reason some assets aren't being included in production
environment during precompilation :( I'll keep you informed as I
understand what is happening...
Em 26-03-2013 11:07, Rafael Mendonça França escreveu:
So I think I didn't changed it yet, but it is on my TODO list.
About your issue, right now I can't take a look. It is assigned to
Guillermo and I know he is a busy person, so I don't know when he will
have time to fix it. If you need this fixed Please Do Investigate.
Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca
On Tue, Mar 26, 2013 at 9:36 AM, Rodrigo Rosenfeld Rosas
<[email protected] <mailto:[email protected]>> wrote:
Em 26-03-2013 00:00, Rafael Mendonça França escreveu:
Have you checked on Rails 4? I'm pretty sure I changed this.
If you changed this it was after the beta release, right? I'm
saying that because my application is using Rails 4 beta and
renders a single space...
By the way, this issue is still affecting my application under
production (I'm using an ugly workaround currently):
https://github.com/rails/rails/issues/9461
Best,
Rodrigo.
On Mar 25, 2013 11:49 PM, "Rodrigo Rosenfeld Rosas"
<[email protected] <mailto:[email protected]>> wrote:
I see.. But working around a Safari's bug doesn't sound like
a good reason to me... Maybe that bug has been already fixed
a long while ago and maybe that Safari version with the bug
hasn't been used for a while...
Maybe the proper solution by that time would be to create a
config option like:
config.support_buggy_safari = true
It could even be the default... But the final choice to
support it or not would come from the application developers.
It fixed an issue by creating another one with regards to how
jQuery handles empty responses in special ways...
For instance, suppose you intercept all JSON results setting
a global error handler. Suppose that handle will check if the
error response contains an error message in the JSON encoded
response. But for a destroy action, for instance, there's
nothing useful to return, so "head :ok" is perfectly fine.
And it would work if the response was truly empty instead of
a single space response...
Cheers,
Rodrigo.
Em 25-03-2013 23:37, Anthony Richardson escreveu:
Hi,
That very response links to the explanation
http://stackoverflow.com/questions/3351247/how-to-return-truly-empty-body-in-rails-i-e-content-length-0
As to whether its still valid to do so is another question.
Cheers,
Anthony
On Tue, Mar 26, 2013 at 1:03 PM, Rodrigo Rosenfeld Rosas
<[email protected] <mailto:[email protected]>> wrote:
Why returning a single space when using "head :ok" for
instance?
See discussion around it here:
http://stackoverflow.com/a/12824527/557368
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
