jQuery 1.8 and modernizr loaded twice

@Neofelis1985 respectfully, could you read your last sentence and explain that you mean by that?

Are you using a subtheme and what version?

@neofelis1985 thanks for the note. Have you actually downloaded the http://foundation.zurb.com/download.php and looked at the HTML structure. Unless I'm missing something it's the same as the theme and this theme is used and production so I didn't notice any issues and that's how it is when you download from the foundation website (See code below) so I just think you might be concerned over nothing unless I'm missing something. If you have an issue related to foundation code kindly file issues in their github queue.

  <script src="javascripts/modernizr.foundation.js"></script>
  <!-- Included JS Files (Compressed) -->
  <script src="javascripts/jquery.js"></script>
  <script src="javascripts/foundation.min.js"></script>
  

I'm seeing a similar issue using the dev version downloaded today (I'm not using a subtheme as I'm only just starting development of the site).
In the HTML page output, I can see the following script definitions:

<script type="text/javascript" src="http://localhost/wdcs/sites/all/themes/zurb-foundation/js/jquery.js?v=1.8.2"></script>
...
<script type="text/javascript" src="http://localhost/wdcs/sites/all/themes/zurb-foundation/js/foundation.min.js?miiire"></script>

The problem is that foundation.min.js contains the jQuery library code. So, jQuery is being initialised twice. This causes a problem because I'm using drupal_add_library to include the jQuery UI datepicker component and the js file for this appears in the list of js files in the HTML, between the jquery.js script reference and the foundation.min.js script reference. Therefore, jQuery gets loaded, the datepicker plugin gets added, and foundation.min.js reloads jQuery thus obliterating the jQuery plugin.

In addition to this, the current foundation release contains jquery 1.9(!) included in the foundation.min.js and that causes the drupal overlay to crash, as it is not compatible with jquery >=1.9...

@johnvb I see what's going on. If I get rid of adding jquery.js there is no way for the sub theme to override and no check for the jQuery update module. If I dump foundation.min.js foundation elements wont work. I think it might be best to remove them both from the repo (and actually they shouldn't be there anyway) and force themers to make decisions based on their use case/project. Thoughts?

Also, FYI to complicate things there is good possibility Foundation 4 won't use jQuery but a different JS library...

@derMatze please review the project page as it has ways of dealing with different jQuery versions (#1779484: Depends on jquery 1.7).

#1779484: Depends on jquery 1.7 is about how to deal with "normal" included jquery versions. But this one (1.9) is implemented from within the foundation.js as mentioned above.
But if you just cut this part from the foundation.js file, everything should be ok :).

@derMatze thanks for your note. Well, that means I would have to maintain my own foundation.js file without it or I have to include the files individually in the info file? Suggestions?

I'm pretty sure, that foundation.min.js doesn't need to be included at all, as it just includes the other js files within one file:
- Modernizr
- jquery
- jquery custom forms
- jquery event move
...

All these files are still as single js files in javascripts folder.

@derMatze good point. For now I'm just removing the duplicate jQuery and Modernizr from foundation.min.js once Foundation 4 comes out I might restructure thanks for the input.

Right now i'm in the "tweaking" and "optimizing" phase on my latest project and i just noticed, that this is still (or again) an issue:

The foundation.min.js in the 1.0-alpha1 release contains a minified jquery 1.8. version.
This was causing *no* errors or bugs so far but by deleting this unnecessary code (jquery and modernizr) i was able to reduce the foundation.min.js file size by roughly 120kb and everything is working flawlessly.

ishmael has indicated it was fixed in dev- therefore the change won't be in alpha1 until another release is created. I believe focus is on 4.x branch now (Foundation 4).