We'll respond shortly.
label.js, which is custom matcher code that Webrat injects into Selenium at run-time (EEK –ed.). That code was not IE7 compliant. The team decided to fork Webrat, pull out selenium-rc and use their own selenium-rc gem to solve the problem. There’s a Lighthouse ticket for this this issue.
default_scope– This is a great idea, but it’s not yet ready for prime time. It can’t be arbitrarily chained with ActiveRecord associations (much like
acts_as_paranoidwas originally implemented) – so you need to add calls it to the end of your chained association & scoping calls. Which doesn’t really make it default, does it?
1.6*. The Mine will now require Java 1.6, which is known to have snappier garbage collection. (I tried this today and found fewer beach balls of tranquility. YMMV. –ed.).
Is Rails’ built-in
protect_from_forgeryworth using? Does anyone turn it off?
The overall consensus is, “Of course we use it! Why would you turn off this default?” Well, It’s a little bit of pain when you’re constructing your own Ajax requests – it breaks perf tests, but it’s turned off for other tests. You may get Invalid Authenticity Token exceptions. (Joseph?)
How do you aggregate results of background tasks in a nightly report?
At least turn on the
cron flag for emailing you results of
cron jobs. Or, look at Delayed Job. Since tasks live in the database, you could make a status page or have another job to mail a report.