GitHub.io
Added link in readme to AngularJS directive

A link to the AngularJS directive for Picturefill I developed was inserted under the Support section of the readme. The directive works with Bower and links to a working demo of an Angular implementation.
Merge pull request #117 from aaronraimist/patch-1

github.io
Merge pull request #122 from tinacious/master

Added link in readme to AngularJS directive
Fixed indenting in picturefill.js
Merge pull request #132 from PeterGok/IndentingFix

Fixed indenting in picturefill.js
Only add img[alt] when [data-alt] exists

Fix a bug where, when the element specified by [data-picture] did not have
a [data-alt] attribute, the generated image element would have an [alt]
attribute set to the string value "null".

<span data-picture> => <img alt="null" src="...">

Now, the following hold:

<span data-picture> => <img src="...">
<span data-picture data-alt=""> => <img alt="" src="...">
<span data-picture data-alt="alt text"> => <img alt="alt text" src="...">
Merge pull request #158 from bryanburgers/alt-bug

Only add img[alt] when [data-alt] exists
Update README.md

IE9 regression bug should not affect IE8 or IE10.
small doc-block typo
fix elements selection

In browsers that support srcset, don’t exclude img elements that also
have a ‘sizes’ attribute, which isn’t supported for now. We should add
precise feature detection, really.

+ wondering how we can manage when `400w` is used in srcset but
`sizes=“100vw”` is implied but omitted (this isn’t supported by any
browser either afaik)
Merge pull request #181 from jkerr838/README.md

Update README.md
Merge pull request #182 from gBokiau/small-typo

small doc-block typo
Create CONTRIBUTING.md
Added a note on scope

Picturefill aims to polyfill the standard features of the `picture` element and related `srcset`, `sizes`, `type`, and `media` attributes (some of which work on `img` elements without a `picture` parent as well). Issues and contributions that fall outside of this scope are not likely to be accepted by the project. Some exceptions include workarounds that improve browser support for standard features.
starting edits to index and readme
index edits
fix candidate selection

previous ascendingSort() wasn’t doing much, since not returning -1 when
resolution ‘a’ was smaller than that of ‘b’. I fixed this ( - instead
of >) but also resorted to ascending sorting.

The logic now goes that we start with the highest resolution available,
then go down gradually until we find the last one that is above the
Dpr. This solves the situation where all available images are below Dpr
(previously the lowest candidate would have been served, now the
highest is being served)
fix (should have tested more)
index edits