10
I Use This!
Very Low Activity

News

Analyzed 26 days ago. based on code collected 27 days ago.
Posted over 15 years ago
When Modernizr was originally released in July, requests came in right away for seeing it hosted on code repositories like Google Code or Github. The promise at the time was: "once it goes 1.0". We had only one real reason for not doing so right ... [More] away: the choice of which public repository service to use. At the time, Modernizr's code base was created and managed pretty much solely by myself, and my experience with these repositories was pretty limited. I didn't want to commit to one only to realize halfway through the next release that I preferred another. Well, Modernizr has since gone 1.0 and not only that, but the project has a new code lieutenant. Paul Irish will take on the role of governing Modernizr's codebase, with me taking a slightly more backseat spot in overseeing the general direction of the project. In other words, I'll play a more directorial role whilst Paul will deal with the specifics of the library's codebase. Paul's skill and talent is already widely recognized and we feel he is a great fit for the role of code lieutenant for Modernizr. His first assignment was to choose a code repository he felt most appropriate for Modernizr. We discussed the various pros and cons with regards to our needs (codebase, feedback, support tickets and so on) and what each service provides, and the choice has settled on: Github. In the coming days, Modernizr will start living on Github and the Modernizr.com site will be updated to direct visitors there instead. Once there, everyone will be able to contribute to and work on Modernizr directly, making the library even better. Meanwhile, please welcome Paul as formal code lieutenant. [Less]
Posted over 15 years ago
When Modernizr was originally released in July, requests came in right away for seeing it hosted on code repositories like Google Code or Github. The promise at the time was: "once it goes 1.0". We had only one real reason for not doing so right ... [More] away: the choice of which public repository service to use. At the time, Modernizr's code base was created and managed pretty much solely by myself, and my experience with these repositories was pretty limited. I didn't want to commit to one only to realize halfway through the next release that I preferred another. Well, Modernizr has since gone 1.0 and not only that, but the project has a new code lieutenant. Paul Irish will take on the role of governing Modernizr's codebase, with me taking a slightly more backseat spot in overseeing the general direction of the project. In other words, I'll play a more directorial role whilst Paul will deal with the specifics of the library's codebase. Paul's skill and talent is already widely recognized and we feel he is a great fit for the role of code lieutenant for Modernizr. His first assignment was to choose a code repository he felt most appropriate for Modernizr. We discussed the various pros and cons with regards to our needs (codebase, feedback, support tickets and so on) and what each service provides, and the choice has settled on: Github. In the coming days, Modernizr will start living on Github and the Modernizr.com site will be updated to direct visitors there instead. Once there, everyone will be able to contribute to and work on Modernizr directly, making the library even better. Meanwhile, please welcome Paul as formal code lieutenant. [Less]
Posted over 15 years ago
I'm very pleased to announce Modernizr 1.0, the first major milestone release of the JavaScript library that detects native implementations of HTML5 and CSS3 features in browsers. Before I tell you about all the useful new features that Modernizr ... [More] 1.0 detects for, I want to express my immense gratitude to, first and foremost, Paul Irish and Ben Alman. The two of them restructured most of Modernizr's 0.9 codebase, leaving it functionally intact but reducing the file size by a stunning 35% and improving performance here and there. I also want to thank John Resig, Mark Pilgrim, Leonid Khachaturov, John Tantalo and Peter Speck. All of whom have made contributions in direction and/or code. So what's new in Modernizr 1.0? To start off, Modernizr 1.0 can now be included in the head section of your website. We've changed its behavior so that it adds the classes—which represent each browser's native implementations—to the html element instead of the body element. See the notes below for details on this. Let's get to the features! We now detect for native browser support for the HTML5 audio and video elements, as well as the Geolocation API. We've also added a second test for Canvas, specifically for Canvas Text. This because various browsers support Canvas drawing but not yet Canvas Text, and the ability to draw text in a Canvas is rather significant and thus warranted its own test. Moving on, we've added a series of tests for HTML5 input data types, such as input type="search" and input type="range". All of these are combined into an array that's accessible from the JavaScript Modernizr object, under Modernizr.inputtypes. Full details are available in the new Documentation area. Last and most certainly not least is the new @font-face detection, courtesy of some more work by Paul Irish. That's right, with Modernizr you can now detect whether a browser will actually render embedded @font-face fonts or not. This, like everything else in Modernizr, is an actual feature detection test. Note: we're cheating a little in the @font-face test because we let IE5 and above pass the test directly; IE supports the standardized @font-face syntax but it only supports EOT fonts. Browsers that support @font-face font embedding with OpenType and/or TrueType fonts are tested using a custom one-glyph font that Paul created, and which is now part of Modernizr in Base64. With all these new tests and additions and even a font glyph inclusion right there in the JavaScript, you may be wondering what the new file size is. The answer: 16kb normal, slightly over 7kb minified. Important questions answered Is Modernizr 1.0 fully backwards-compatible with 0.9? Yes and no. As far as the JavaScript side is, yes, you should be able to just replace the old 0.9 with the new 1.0 file and adjust your script include path accordingly, and everything should Just Work. However, as mentioned above, the CSS side has one crucial change: Modernizr 1.0 adds the various class names to the html element instead of, previously, the body element. Thus, if your CSS rules say body.csstransforms, you'll have to change them to read either just .csstransforms or html.csstransforms. Is this valid? Yes, under HTML5—which is what Modernizr is meant to be used under—it is perfectly valid to put a class attribute on the html element. It works just fine on HTML4 and XHTML documents, but it won't validate. (but remember: validation is a tool, not a goal) Additional note: Modernizr 1.0 also checks for (and if found, removes) the class no-js from the html element. In its place, it adds the class js, which means that if you start your templates with the code <html class="no-js"> and then include the Modernizr library, you can use the classes .no-js and .js to respectively determine whether JavaScript is disabled or enabled in the browser. Will Modernizr go on Github / Bitbucket / similar now that it is 1.0? Yes, very soon it will get hosted on a public repository so that people can contribute a little more directly. We haven't decided yet which one, but no new releases will be made until it's hosted publicly. What do you have planned for the next release? Wait and see! Fortunately, we've now added a News section and RSS feed to Modernizr.com, so you can simply subscribe to the feed and we'll keep you posted of all things Modernizr. Now go and download Modernizr 1.0! [Less]
Posted over 15 years ago
I'm very pleased to announce Modernizr 1.0, the first major milestone release of the JavaScript library that detects native implementations of HTML5 and CSS3 features in browsers. Before I tell you about all the useful new features that Modernizr ... [More] 1.0 detects for, I want to express my immense gratitude to, first and foremost, Paul Irish and Ben Alman. The two of them restructured most of Modernizr's 0.9 codebase, leaving it functionally intact but reducing the file size by a stunning 35% and improving performance here and there. I also want to thank John Resig, Mark Pilgrim, Leonid Khachaturov, John Tantalo and Peter Speck. All of whom have made contributions in direction and/or code. So what's new in Modernizr 1.0? To start off, Modernizr 1.0 can now be included in the head section of your website. We've changed its behavior so that it adds the classes—which represent each browser's native implementations—to the html element instead of the body element. See the notes below for details on this. Let's get to the features! We now detect for native browser support for the HTML5 audio and video elements, as well as the Geolocation API. We've also added a second test for Canvas, specifically for Canvas Text. This because various browsers support Canvas drawing but not yet Canvas Text, and the ability to draw text in a Canvas is rather significant and thus warranted its own test. Moving on, we've added a series of tests for HTML5 input data types, such as input type="search" and input type="range". All of these are combined into an array that's accessible from the JavaScript Modernizr object, under Modernizr.inputtypes. Full details are available in the new Documentation area. Last and most certainly not least is the new @font-face detection, courtesy of some more work by Paul Irish. That's right, with Modernizr you can now detect whether a browser will actually render embedded @font-face fonts or not. This, like everything else in Modernizr, is an actual feature detection test. Note: we're cheating a little in the @font-face test because we let IE5 and above pass the test directly; IE supports the standardized @font-face syntax but it only supports EOT fonts. Browsers that support @font-face font embedding with OpenType and/or TrueType fonts are tested using a custom one-glyph font that Paul created, and which is now part of Modernizr in Base64. With all these new tests and additions and even a font glyph inclusion right there in the JavaScript, you may be wondering what the new file size is. The answer: 16kb normal, slightly over 7kb minified. Important questions answered Is Modernizr 1.0 fully backwards-compatible with 0.9? Yes and no. As far as the JavaScript side is, yes, you should be able to just replace the old 0.9 with the new 1.0 file and adjust your script include path accordingly, and everything should Just Work. However, as mentioned above, the CSS side has one crucial change: Modernizr 1.0 adds the various class names to the html element instead of, previously, the body element. Thus, if your CSS rules say body.csstransforms, you'll have to change them to read either just .csstransforms or html.csstransforms. Is this valid? Yes, under HTML5—which is what Modernizr is meant to be used under—it is perfectly valid to put a class attribute on the html element. It works just fine on HTML4 and XHTML documents, but it won't validate. (but remember: validation is a tool, not a goal) Additional note: Modernizr 1.0 also checks for (and if found, removes) the class no-js from the html element. In its place, it adds the class js, which means that if you start your templates with the code <html class="no-js"> and then include the Modernizr library, you can use the classes .no-js and .js to respectively determine whether JavaScript is disabled or enabled in the browser. Will Modernizr go on Github / Bitbucket / similar now that it is 1.0? Yes, very soon it will get hosted on a public repository so that people can contribute a little more directly. We haven't decided yet which one, but no new releases will be made until it's hosted publicly. What do you have planned for the next release? Wait and see! Fortunately, we've now added a News section and RSS feed to Modernizr.com, so you can simply subscribe to the feed and we'll keep you posted of all things Modernizr. Now go and download Modernizr 1.0! [Less]