I'm using a Macbook pro 13' and when clicking on any of the items, I'm not able to see the call to action buttons in the modal dialog.

Attaching the screenshot below

label: Bug

Seems like the modal dialog css using a max-height: 100%; is causing the issue.

I added vevo a while back, what's the approval process like?

#255

doooble.com no longer hosts an app (seems to be sedo parking).

Take a look at #112
This commit still has comments in the json.
This is preventing json to be parsed.

when I click on any of the items in the menu, nothing happens.

My application works in IIS server, not node.js. Is it possible to participate?

I just released our new component framework which is based on AngularJS.

My use of AngularJS is a little unique. I am using angular as the UI framework for our Thirdparty JavaScript library which services over 400 domains across our network. I would love to add our service to the registry since we have a pretty large footprint with many thousands of visitors interacting with our UI everyday.

Is there anyway I could easily express this in the current JSON format?

I realize when having a lot of pages, the pagination repeater became too long and sometimes wrap in the container.

The following code allows you to have ellipses (...) in between (similar to 500px's pagination, see http://500px.com/photos)

Markup:

<li ng-repeat="n in range(pagedItems.length)" ng-class="{active: n == currentPage}">
    <a ng-bind="n + 1" ng-show="n >= 0" ng-click="setPage(n)">1</a>
    <span ng-show="n < 0">...</span>
</li>

Range function (might have to tweak the numbers):

$scope.range = function(start, end) {
    var ret = [],
        i;
    if (!end) {
        end = start;
        start = 0;
    }

    for (i = start; i < end; i++) {
        ret.push(i);
    }

    var paging = ret;
    if (ret.length > 6) {
        var currentPage = $scope.currentPage;
        paging = ret.slice(0, 1);
        if (currentPage === 0) {
            //shows 1, 2, 3 ... 8, 9, 10
            paging = paging.concat(ret.slice(1, 3));
            paging.push(-1);
            paging = paging.concat(ret.slice(ret.length - 3, ret.length));
        } else if (currentPage < 4) {
            //shows 1, 2, 3, 4, 5 ... 10
            paging = paging.concat(ret.slice(1, 5));
            paging.push(-1);
            paging = paging.concat(ret.slice(ret.length - 1, ret.length));
        } else if (currentPage >= ret.length - 4) {
            //shows 1 ... 6, 7, 8, 9, 10
            paging.push(-1);
            paging = paging.concat(ret.slice(ret.length - 5, ret.length));
        } else {
            //shows 1 ... 4, 5, 6 ... 10 for example
            paging.push(-1);
            paging = paging.concat(ret.slice(currentPage - 1, currentPage + 2));
            paging.push(-1);
            paging = paging.concat(ret.slice(ret.length - 1, ret.length));
        }
    }
    return paging;
};

If you refresh a page with the modal open sometimes it works, sometimes the modal flashes open and instantly closes leaving the url in a wrong state.

The issue is in bwa.js line 39 and 99.

The popstate event fires in chrome on the first load with an ev.state of null. This would set lightbox to null which results in the modal being closed.

The success handler for the get request on project.json also updates lightbox checking if a project matches the current url. If there is a match it sets the lightbox to the project which results in the modal being open.

What I think happens is that the project.json file request finishes first and sets the lightbox to the project which has the modal begin to open. Then the onpopstate event handler fires which immediately closes the modal leaving the url in a wrong state. Using the chrome debugger with breakpoints on 39 and 99 seems to confirm this (if 99 is first, it breaks).

Looking at this stack overflow post (http://stackoverflow.com/questions/6421769/popstate-on-pages-load-in-chrome) it seems like checking if ev.state === null and ignoring that popstate event if so might work, but I'm not sure if that is fully cross browser or would ignore legit events (I've never used the popstate event so don't really know whats valid or not).

As a huge fan of Angular, I think it would be really great for marketing/PR reasons to prioritize and showcase higher-profile projects on the builtwith front page, instead of the unsorted order they're in right now (except for the YouTube app which is showcased), which makes Angular seem like it's basically just used for toy projects.

For example, Doubleclick should be on the front page, instead of buried on page 4.

This project is not actively maintained by collaborators. @IgorMinar Please check the pull requests so that these can be added to the builtwith.angularjs.org website.
Many of these projects look very interesting.

Just wanted to have a look at the new projects. The links are gone from http://builtwith.angularjs.org/ however.

we need to enable deeplinking for pagination

I'm using firefox and when I click on the "Balance Projector" the popup takes up the entire screen, pushing the "Check out the app" and "View the source" buttons off the page.

It would be great to be able to reference the state with the selected tags like http://builtwith.angularjs.org/#tag#opensource

Looks like it's related to #37, @IgorMinar @ericduran, what do you think?

Params:
Chrome 38
Ubuntu 14.10

it's listed with:

http://http//wordcharconvertor.rogtopia.com/

should be:

http://wordcharconvertor.rogtopia.com/