Hey Gregory, Gregory Seidman a écrit : > I've been upgrading a Rails 1.2.5 webapp to use the newly release prototype > 1.6 and script.aculo.us 1.8. One thing I ran into was a bizarre change to > the defaults for Ajax.InPlaceEditor. First off, I can sort of understand > how it might make sense to expect an HTML (rather than JS) response from > the Ajax request, but it would seem to make more sense to autodetect based > on the returned MIME type if no setting for the htmlResponse option is > given.
IIRC, the current behavior is backawards-compatible with the old IPE code (however, it's not as spiffy as the new Ajax.Response thing, granted; the IPE code was developed around Prototype 1.5.1 and doesn't always seize the whole power of 1.6.0). > Second, and a much bigger deal, is that the Ajax request is being defaulted > to a GET instead of a POST. Given that this is semantically an edit (it's > even in the name!), it really should be a POST (and the web server should > not respond to a GET request by changing state). Why should it default to > GET? What's the justification behind that change? INDEED! Copy/paste error from another part, I guess. Definitely incorrect as per W3C rec's and plain common sense. I'm swamped right now, can you please file a clean ticket about this? The patch is a one-liner, but some specific tests would be nice to warrant inclusion in the trunk. I'll try and find some time soon for this, unless Thomas jumps in and whacks the bug down. Thanks for the heads up, -- Christophe Porteneuve aka TDD [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
