Yepnope is deprecated and will no longer be included in Modernizr v3. Official statement on deprecation is here: https://github.com/SlexAxton/yepnope.js#deprecation-notice

Update 2015-09: Modernizr v3 loader release is accelerating the need for this changem since as of now, it's no longer possible to generate a custom build with a script loader.

I have long taken the position that the Modernizr Drupal module would only support the latest version of Modernizr JS library. Given the architectural changes between Modernizr v2 and v3, I think it's time to adjust that position and freeze support for the module to a major version.

So for the record, Modernizr Drupal module 7.x-3.x will forever support Modernizr v2. The upgrade would be way too dirty for me to handle as a lone contributor. Despite getting many excellent bug reports and contributions from folks in this queue, my daily paid work does not bring me close enough to this module to reliably provide an upgrade.

I would like to start working on Modernizr Drupal module 7.x-4.x and prioritize Modernizr v3 support over all other things. AFAICT this means removing features, and hopefully that process will be relatively easy. I would also like the 8.x branch (which is another task I'm not really keen to handle on my own) to branch from 7.x-4.x, making Modernizr v2 support a low priority in Drupal 8.

Comments

dddbbb’s picture

Fair enough :)

Tis a shame though that this project's version numbers don't match that of Modernizr's - I can see that causing a little confusion.

E.g.

7.x-2.x uses Modernizr v2
7.x-3.x uses Modernizr v3
...

rupl’s picture

FWIW this has been a (very) minor point of disappointment for me too since I began working on this module, but Tamás and I agreed at the beginning that all my work providing APIs to support a purely client-side library would go in 7.x-3.x since his employer desired cookie-based server-side functionality contained in 7.x-2.x

rupl’s picture

Category: Task » Plan
Issue summary: View changes

well, shucks. This won't be possible, because the v2 Modernizr builder is not online anymore. Two major code changes need to happen:

  • The actual part which interacts with the builder is not so complicated. I made a big include with all the tests. I think that part isn't so hard to update.
  • As for handling the lack of Modernizr.load: #2568311: Make Modernizr.load optional
rupl’s picture

Issue summary: View changes

  • rupl committed eed3077 on 7.x-3.x
    Issue #2311603 by rupl: update version regex
    
rupl’s picture

Status: Active » Closed (fixed)

7.x-3.5 provides support for Modernizr v3. This is donezo.