Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "Bump jquery-rails version to prevent breakage."
As it turns out, jQuery 1.8 has a few bugs in it. We'll suggest jquery-rails 2.0 for the time being. This reverts commit c547ad5.
- Loading branch information
1 parent
c547ad5
commit ea24cd6
Showing
3 changed files
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -68,4 +68,4 @@ group :assets do | |
gem 'uglifier' | ||
end | ||
|
||
gem 'jquery-rails', '~> 2.1.0' | ||
gem 'jquery-rails', '~> 2.0.0' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ea24cd6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@robyurkowski still an issue?
ea24cd6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I too am curious.
ea24cd6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was tested in IRC and we had a bunch of tests fail still. Someone is free to check if jQuery 1.9 will solve the issue, but I think this will have to stay into place until jQuery becomes compliant or we throw in the towel.