This past week included four significant announcements:

• The Dojo Tutorial series has been updated to include version 1.7 of Dojo. Read the announcement from SitePen for more details.
• Wink Toolkit has been updated to version 1.4.1. Wink Toolkit is a Dojo Foundation project that is mobile-specific, now builds on AMD, and is now easy to use with Dojo. See the Community Connections demo app which shows off using Dojo and Wink together, and introduces some of the committers to Dojo and Wink.
• CometD has released version 2.4.0. In addition to improving their WebSockets support, they have also updated their Dojo client to work with Dojo 1.7.1 (though it does not yet support AMD).
• We’ve long heard that we have issues with our documentation, and in spite of our best efforts to improve them, especially with the tutorials, we need help identifying and resolving issues with our docs. If you’re interested in contributing, less us know on the mailing list or on IRC. But even if you’re not interested in that level of help, we’ve simplified the feedback process. At the bottom of each API viewer and tutorial page (and soon reference guide as well), you’ll find a link to a quick feedback form. If you see an issue on the page you’re reviewing, simply click the link, type in a note with the details of the problem, and we’ll make it a priority to fix.

Just referencing the list of bugfixes, as most team members were absent this week or busy with unresolved tasks:

Bugfixes

For a complete list of tasks accomplished during the last working week, use this bugzilla query.

Have a nice weekend.

Lots of changes in the Network inspector have now made it into an experimental build. The main purpose of the makeover is to give more insight on what happens on the Network side of Opera, with powerful new filtering and search functionality.

The type filter now lets you narrow down the view to certain types of Resources. In addition, you can also look only at the Resources that were requested via XMLHttpRequest. Also you can use CTRL/CMD + click, to combine multiple filters.

We have added an inline search, which works consistently over the URL list, table view, and in the details.

The graph view now uses specific colors to represents the different phases of resource retrieval as segments within each row. A new tooltip lets you see a sequence of internal events in Opera that occur during the retrieval and how much time was spent on each. Note that the values represent the time elapsed between two events.

Although the standard graph view is useful for visualizing the loading flow, sometimes developers may be more interested in picking out specific data about their requests. You can now switch from flow view to a table view, which can be sorted and further customized via the context menu.

Selecting each line will provide the specifics of each request in the Details view, which shows the actual request and response of each network activity, including headers and body. This view has been streamlined: headers are split into key/value pairs, and the response body is shown inline.

Most of these UI changes are still work in progress, but they should give you an indication of where we're heading. A few known issues:

• The line-height of tables can get out of sync with the list of URLs on the left-hand side
• Content tracking is not enabled by default, but available as a toggle in the Network options tab. Without tracking, the response body will sometimes not be shown in the Details view
• The search may sometimes match parts of the UI itself
• The layout in the details view sometimes breaks due to long headers or body
• Timing information in the Network view is not accurate, as it can be affected by other debugging activities in Opera. In general, the loading flow will be slower when Opera Dragonfly is running. We plan to address this issue with a special network-profiler mode, which is on the roadmap for later this year.

But wait, there's more! As a bonus, this build also includes some new features in our Style inspector. We now show color swatches next to all color values. And – as hotly requested by many of our users – it's now possible to use your preferred color format: Hex, RGB or HSL (which can be changed in Settings → Documents → Styles). Other changes include clickable links (which open in the Resources tab) and a streamlined view in the Computed Style panel.

Hey there Internets, it’s the jQuery Core team! We haven’t talked in a while, but over the holidays we were busy fixing the bugs you reported. The result of that hard work is jQuery 1.7.2 Beta 1. We decided to get a beta out by Groundhog Day so you wouldn’t be in the shadow of six more weeks of unfixed bugs.

You can get the code from the jQuery CDN:

• http://code.jquery.com/jquery-1.7.2b1.js

Oh, we know what you’re thinking: “Cool, a new version of jQuery; I’ll wait until the final release has been out a few weeks and then I’ll give it a try.” Right, and then you’ll find some bug that keeps you from upgrading. Nothing makes us sadder than finishing up a release and only then seeing a report of a serious bug that could have been fixed earlier.

So please, come out of your burrow and try this beta with your code. Did we miss an old bug? Did we create a new bug that makes you feel like Bill Murray waking up to “I Got You Babe?” We want to know. You can use the bug tracker to report bugs; be sure to create a test case on jsFiddle so we can figure it out easily. If you’re not sure it’s a bug, ask on our forum or on StackOverflow.

jQuery 1.7.2b1 Change Log

The current change log of the 1.7.2b1 release.

Ajax

• #10978: jQuery.param() should allow non-native constructed objects as property values

Attributes

• #5571: Allow chaining when passing undefined to any setter in jQuery

Build

• #10692: Configure the jshint options to more accurately match the style guide
• #10902: ability to test a built version of jQuery in unit tests
• #10931: Unit tests shouldn’t require internet access

Core

• #10466: jQuery.param() mistakes wrapped primitives for deep objects

Css

• #10639: outerWidth(true) and css(‘margin’) returning % instead of px in Webkit
• #10754: have jQuery.swap return the return of the callback instead of just executing it
• #10782: Incorrect calculating width
• #10796: Bug in IE7 with $(‘#el’).css.(‘background-position’)
• #10858: css.js regular expressions are incomplete
• #11119: The curCSS function only need 2 arguments

Effects

• #8498: Animate Hooks
• #10006: method show is not working as expected in all browsers when called for document fragment
• #10848: Animation toggling loses state tracking in certain atomic edge cases

Event

• #8165: .live(‘click’, handler) fires on disabled buttons with child elements in Chrome
• #10819: Eliminate “this.on.call(this, “
• #10878: $(“select”).live(“change”, function(){ …broken in IE8 in jQuery 1.7
• #10961: Error in XRegExp using jQuery 1.7.1 in IE6-9
• #10970: The .on() selector parameter doesn’t work with :not(:first) selector
• #10984: Cannot off() custom events ($.event.special)
• #11021: Hover hack mangles a namespace named “hover”
• #11076: .clone(true) loses delegation filters
• #11130: jQuery.fn.on: binding map with null selector ignores data
• #11145: $(document).on() not working with name=”disabled”

Manipulation

• #9427: Passing undefined to .text() does not trigger setter
• #10753: inline the evalScript function in manipulation.js as it’s only used once
• #10864: text() method on a document fragment always returns the empty string
• #11055: Update HTML5 Shim elements list to support latest html5shiv

Misc

• #10952: .fired() doesn’t work on Callbacks object when it is flagged with “once”
• #11257: Wrong path to source files in test suite if PHP missing

Support

• #11048: Support Tests affect layout for positioned elements in IE6-9

Firefox 10 is now available as a free download for Windows, Mac, Linux, and Android. As always, we recommend that users keep up to date with the newest version of Firefox for the latest features and fixes. The release notes for Firefox 10 are available here.

The new Uize.now static method, implemented in the Uize base module, returns the current time in milliseconds since 1970 (POSIX time).

The new Uize.mergeInto static method, implemented in the Uize base module, merges the contents of one or more source objects into the specified target object, and returns the target object as the result.

The new Uize.getClass static method, implemented in the Uize base module, gets the class of which a specified value is an instance, or returns the value if it is a class or function.

The new Uize.toNumber static method, implemented in the Uize base module, lets you coerce a value to a number, with defaulting if it cannot be coerced successfully.

The new Uize.isSameAs static method tests if two values are the same in a strict equality test, with support for NaN values.

The new Uize.isNaN static method, implemented in the Uize base module, returns a boolean value, indicating whether or not the specified value is the JavaScript special value NaN.

The class mechanism that was implemented in the Uize module has been moved out of that module and into the new Uize.Class module.

The new Uize.isList static method returns a boolean, indicating whether or not the specified value is considered a list.

A handful of dummy functions have been added to the Uize base module, that can be used in certain situations where you need to supply a dummy function as a handler, callback, or iterator function.

The JavaScript new operator is now optional when creating instances of Uize subclasses, and you can make the new operator optional for your own object constructors using the newly added Uize.noNew static method.

The Uize.lookup and Uize.reverseLookup static methods have been improved with the added ability to specify a target object for adding entries.

Comprehensive unit tests have been created for the Uize.Data.NameValueRecords module.

The Uize base module has been improved with the addition of the new Uize.forEach and Uize.map static methods.

The Uize base module has been given a boost with the addition of a slew of convenient utility belt features.

The new Uize.Array.Util module provides a home for miscellaneous array utility methods that are not yet deemed ready for promototion to the Uize.Array or Uize modules.