We’re looking for an experienced and passionate front-end engineer to join the Internationalization team at Yahoo! You must have demonstrable mastery of and passion for JavaScript and be well-versed in various front-end technologies. You love solving complex problems at massive scale, have built robust and intuitive APIs that have withstood the test of time, and embrace the best practices of performance, security, maintainability, code reuse, and usability. You also have excellent communication skills, possess great attention to detail, and are independent and resourceful. The position is located in Sunnyvale, CA.

Interested candidates should send a resume and cover letter to yui-jobs (at) yahoo-inc.com

Minimum Job Qualifications

• Absolute mastery of JavaScript.
• Expert in YUI.
• Skilled in HTML/CSS.
• Demonstrated experience building reusable JS components that are modular, performant, and maintainable.
• Strong Java skills using Struts or other MVC framework.
• Experience with Linux/Unix dev environments.
• Knowledge of Maven.

Preferred Job Qualifications

• Knowledge of internationalization processes and platform development desirable.

Special Thanks

In addition to the community at large, special thanks goes out to following individuals for sticking with us during this period of transition and shepherding their pull requests through the new process: @danbeam (Dan Beam), @faisalman (Faisal Salman), @killsaw (Steven Bredenberg), @ademey (Andrew Demey), @sbertrang (Simon Bertrang), @danielbeardsley (Daniel Beardsley), @bmouw, @bandesz, @ryansully (Ryan Sullivan), @apm (Adam Moore), @nlalevee (Nicolas Lalevée), and @tml (Joey Smith).

Changes

• Fixes for “important” and conditional comment processing
• Fixes a bug in the support for JS 1.7 style getters/setters
• Better compliance and improved compression in CSS results
• Many improvements to parameter parsing and batch mode

Join the YUICompressor Community

As we continue to expand our adoption of the new Contributor Model, we invite any who are interested in the progress of YUICompressor to join us on the mailing list, file issues or PRs on the GitHub repo, or just help us spread the word: YUICompressor lives!

If you know of systems that have integrated YUICompressor into their projects or codebases, please drop us a line or add a comment here so we can help push new versions of YUICompressor deeper into the community.

Release Links

• Compare v2.4.8 source code to v2.4.7
• Download the 2.4.8 release
• Download the 2.4.8 source archive

Due to a recently discovered SWF vulnerability, we are releasing YUI 3.10.1. Any project which is self-hosting YUI 3 .swf files should read the security bulletin and take action to resolve potential vulnerabilities on your servers.

YUI 3.10.1 is identical to 3.10.0, with the vulnerable .swf files replaced with patched files. YUI 3.10.1 also reflects fixes in our build system that prevented some files from being included in the release. No other code changes have been included with this release.

You can find YUI 3.10.1 on the CDN, as a download, and on npm.

Special thanks to Aleksandr Dobkin and Sebastian Roschke of the Google Security Team for reporting the issue.

Development continues against our current Development Schedule. Please check out the Change History Rollup for this release.

Deprecated Modules

In accordance with our Deprecation Policy, we are taking this opportunity to announce the deprecation of Simple YUI, and our intention to deprecate all .swf-related features in a future release. Stay tuned to the Contributor Mailing List for ongoing discussion on these topics.

The event itself was a solid 24 hours (although I went home to bed, I’m too old to pull all-nighters) and produced some nice hacks using a range of APIs. I enjoy these hack weekends for the chance to play with APIs that I would not normally have much reason to use, to work with new people, and to learn about new stuff I don’t otherwise come across.

My own effort was the ‘Contextificator‘ – a bookmarklet that tries to make the ‘I wonder what/who/where that is -> select text -> new tab -> search -> read -> return to first page’ pattern I frequently find myself doing. It uses the Yahoo Content Analysis API to look at the page (or text selection), and then pulls out search results, images, wikipedia text, or a map from Yahoo! BOSS and other APIs, and puts it all in a sidebar on the page you’re reading.

I had resolved to try to do things reasonably properly, even though it was a hack. I didn’t want to end up with 24 hours worth of spaghetti code, which is usually what happens. So I did try to structure things properly, extending View and Model and Base where that seemed right, writing and loading them all as separate modules, and so on.

So after about 10 hours I’d done quite a lot of that set up, trying to get a reasonable structure for the code… and all I had to show for it was an empty iframe. At that point I was beginning to feel slightly dispirited. However, the next morning it paid off. It all came together very quickly, which left me enough time to tussle with CSS so that it looked vaguely presentable.

Now on reflection I’m sure that at least some of the overall code design decisions I made were wrong. That’s no surprise. But by the end I was struck again by the strength of YUI and that even in a 24 hour hack I reckon the investment in trying to structure your code properly (instead of a mess of callbacks and dubious hacks) was well worth it. That’s largely because YUI gives you such a strong base to build from and establishes good practices to follow.

So yay to hack weekends. Yay to YUI. And happily the Contextificator won second prize overall, and I got my giant cheque presented by Nick d’Alosio (of Summly fortune – though of course the cheque he got from Yahoo! is several orders of magnitude larger, [and I'm old enough to be your father, dammit])!

(If you’re wondering, it’s called ‘Contextificator’ mainly because my daughter uses a ‘stapleriser’ to make holes in paper.)

About the author: Matt Parker (@Lamplightdb) Matt is creator of Lamplight Database Systems, a powerful and affordable management system for charities. He is also a father of three, trombone and bazouki-ist in Albino, and a lapsed climber. Matt does not get to spend as much time as he would like writing JavaScript.

We continue to rely on Yeti in CI and we’ve fixed a few bugs along the way. Today, we run 17,202 tests in browsers on every YUI library commit using Yeti. An additional 45,665 tests run about once a day. We can easily reach 100,000 tests running daily with our setup (assuming 4 commits per day) and we still have more browsers and devices yet to come.

Changes

• Automatically restart stalled browsers when using WebDriver.
• Avoid Selenium proxy in Sauce Labs to support IE 6-9.
• Maximum duration for sessions in Sauce Labs is now 2 hours.
• Support for HTTP_PROXY and HTTPS_PROXY environment variables when installing Yeti dependencies. Thanks, @ryanvanoss!
• Crash fix: prevent calling _launch twice when starting a browser.
• Crash fix: properly close duplicate connection.
• Bugfix: Yeti exits with code 1 when tests fail using the JUnit XML reporter.
• Bugfix: Fix bug in Batch.disallowAgentId.
• Bugfix: Uncaught exceptions are now reported in JUnit XML results.
• Bugfix: Improve handling of browser-sent events on load.
• Upgrade glob and request dependencies.

Get Yeti

You can upgrade now by running npm install -g yeti. Learn more about Yeti at yeti.cx.

Release Links

• Compare v0.2.21 source code to v0.2.22
• v0.2.22 documentation
• Unit code coverage
• Functional code coverage

The latest set of target environments is always available at http://yuilibrary.com/yui/environments/.

If you have questions about AlloyUI, please feel free to contact Eduardo Lundgren (@eduardolundgren).

Dav Glass (@davglass) kicked things off with updates about Luke Smith and Ryan Grove moving to Reviewer status, as well as Caridy Patino and Juan Dopazo joining the ranks of YUI Committers (for more details about roles in YUI check out our Contributor Model). He also touched briefly on his new position within Yahoo! as architect promoting JavaScript and Node.js. While we are sad that he is moving on from the YUI team, we are glad that he will be acting as a proponent for web technologies within Yahoo! We’ll miss you Dav!

Eric Ferraiuolo (@ericf) was up next with a talk entitled “YUI 3.10.0 Go Fast” that really resonated with the folks at the event – getting several rounds of applause at each slide showing impressive performance gains in BaseCore, Base, CustomTarget, and EventTarget. Check out the YUI 3.10.0pr1 announcement for more details!

Tilo Mitra (@tilomitra) was up next with a talk about his YUI CSS project, featuring clean and simple CSS as a basis for any web project. He showed us the progress he’s made on Responsive Grids CSS as well as components such as lists, tables, and forms. This is an exciting project, and we look forward to more updates from Tilo.

Next up was Ryan Grove (@yaypie) who persevered in attending even though he was not feeling well and gave us a great overview of some of the work he’s been doing implementing Y.Tree, specifically gallery-sm-menu and galler-sm-treeview. His TreeView demo was especially well-received as it boasted impressive performance, rendering tens of thousands of nodes very quickly. He also spoke briefly about some works-in-progress, including a new contentEditable-based WYSIWYG editor.

Closing out the talks was Luke Smith (@ls_n) who gave us an overview of how Y.Promise works behind the scenes and encouraged developers to try out this new way to write asynchronous code in a way that reads more like synchronous code. For further reading about Promises and the A+ spec check out this site.

Once the talks completed, folks broke into informal groups and spent the rest of the evening talking about various YUI-related issues while eating pizza and veggies. Evan Goer (@evangoer) was there as well signing his book “YUI3 Cookbook“.

If you would like to watch the full recorded stream of the event, check out the YouTube video below. Apologies for the poor sound quality! You’ll notice quite a bit of echo in some of the presentations, however they get better near the end. We’re learning as we go, and hope to do more of these open events for the YUI community in the future.

Use Only Launched Browsers

When specifying browsers to launch, Yeti 0.2.21 will ignore browsers that are manually connected and will only use browsers launched by Selenium to test that batch.

Recognize Browsers & Environments Used by Sauce Labs

We’ve included browser names, versions, and OS options that are used by Sauce Labs. We also added latest as a version. New options include:

• Windows 2003
• Windows 2008
• Windows 2012
• Mac 10.6
• Mac 10.8
• iPad
• iPhone

These can be used together to launch browsers like this:

• -b chrome/xp
• -b "ie/6/windows 2003"
• -b "ie/10/windows 2012"
• -b "iphone/6/mac 10.8"
• -b firefox/latest/xp

Full Changelog and Bugfixes

We also fixed a few bugs. The full changelog is below:

• Batches that use WebDriver only use browsers launched by WebDriver, not existing browsers.
• Accept latest as a WebDriver browser version.
• Add browsers used by Sauce Labs.
• Fix server-side wd-url command-line option.
• Fix issue with echoecho JSONP when using a query string like &callback=foo.
• Fix possible hang during WebDriver browser launching.
• Fix possible quit before JUnit XML was completely written to stdout.

Upgrade Now & Release Links

You can upgrade now as usual: npm install -g yeti.

• Compare 0.2.21 source code to 0.2.20
• API documentation
• Unit code coverage
• Functional code coverage

What’s Next

We continue to improve Yeti as we use it to test YUI 3.10.0. Support for HTTP proxies during Yeti’s installation is coming soon thanks to an in-progress pull request by @ryanvanoss which is coming in the next release.

From Caridy:

“Even though this is not a big change for me since I have been working fulltime with Mojito and YUI team for the last 6 months, I’m stoked to formally become part of the team.”

Caridy cited his goal of joining the YUI team as reason why he originally joined Yahoo! and “… here I am now, working with this group of friends that are incredibly talented and passionated about the frontend discipline.”