| Issue 299: | Add Modernizr to the AJAX Libraries API | |
| 820 people starred this issue and may be notified of changes. | Back to list |
Modernizr (http://www.modernizr.com/) is a library to detect CSS 3 features and enables styling of HTML 5 elements in older browsers.
Comment
1
by
rob.mira...@gmail.com,
Jun 15, 2010
,
Jun 22, 2010
yes pls!
,
Jun 22, 2010
Yes pleas. For better caching
,
Jun 23, 2010
Would be great!
,
Jun 23, 2010
FTW
,
Jun 24, 2010
Я тоже голосую за добавление!
,
Jun 29, 2010
(No comment was entered for this change.)
Labels: -Type-Defect Type-Suggestion APIType-Libs
,
Jul 15, 2010
Still waiting!
,
Jul 15, 2010
I am waiting since mklickman1 told me to via tweet.
,
Jul 15, 2010
This would be awesome. I might give you a cookie, Google. You want cookies? I heard you like cookies. Mmmmm...
,
Jul 15, 2010
Do it. Go on, do it.
,
Jul 15, 2010
I would also want to second that request. Modernizr would be a great library in google apis.
,
Jul 23, 2010
Add to repository!
,
Aug 6, 2010
it would be awesome.
,
Aug 6, 2010
I'm not sure Modernizr is the end-all-be-all for this kind of thing, but it does work and it's widely used. I would find it helpful to have it up on Google's CDN. Thanks for your consideration, Google Gods!
,
Aug 7, 2010
I would love for Modernizr to be hosted by google ajax apis. Now if only Filament Groups EnhanceJS and Remy Sharp's HTML5Shim can be hosted...........
,
Aug 10, 2010
Please, host it with Google CDN indeed.
,
Aug 10, 2010
If you want support added, you need to STAR this issue. Please stop adding comments requesting support. Spamming everyone who is following the guidelines will only make people want to un-star this issue.
,
Aug 10, 2010
Yes, please stop replying to this issue. Haha, irony!
,
Sep 9, 2010
pretty please
,
Sep 10, 2010
I just learned of Modernizr, and would love to see it added to the api.
,
Sep 15, 2010
this needs to happen
,
Sep 26, 2010
starred
,
Oct 3, 2010
do it!
,
Oct 6, 2010
i'd like to see modernizr get added to the api!
,
Oct 15, 2010
Yeah baby.
,
Nov 3, 2010
Thumbs up!
,
Nov 6, 2010
Go for it!
,
Nov 6, 2010
Would be great
,
Nov 6, 2010
OK, it's been said before but people seem to keep missing it, so I'll say it once more before I un-star the issue: *****IF YOU WANT TO SUPPORT THIS ISSUE, THEN STAR IT, DON'T ADD A COMMENT.**** If you add a comment, it sends an email to everyone who has starred the issue, and your "yes please" isn't going to help convince Google. What will help is for it to have lots of stars, showing support for the issue. Adding useless comments means people (like me) are likely to un-star it to avoid getting all the emails, so it's counterproductive. Yes, I know that by adding this I'll be doing the same and it's so ironic/hypocritical etc etc, but I think it's probably worth one more email if it stops people adding more useless comments. Thank you and good night.
,
Nov 10, 2010
(No comment was entered for this change.)
Labels: -Type-Suggestion Type-New-Library
,
Feb 14, 2011
please add!
,
Mar 7, 2011
Yes!
,
Mar 29, 2011
If you're looking for a CDN that hosts Modernizr here are two: http://www.cdnjs.com/ http://api.yandex.ru/jslibs/
,
Mar 29, 2011
@Wrum, Thanks, but not this is a request for people looking for reliability and speed of the Google CDN, rather than other 100s of other CDNs that continue to popup and down over time. Everyone, be sure to "star" the item, as comments do not help the cause. This is a common problem across all of Google Code. Google is not known for their user experience, and thus people will continue to comment rather than star, until Google makes it a better experience for users.
,
Apr 12, 2011
Is Google ignoring this to push Google Chrome Frame?
,
Apr 12, 2011
please~
,
Apr 13, 2011
I want it, too.
,
Apr 13, 2011
Since tobyyun and mctenshi (among many other people), seem to be illiterate, and can't understand that only staring the issue will bring it to Google's attention, I'm going to unstar it. It doesn't look like Google will be adding it anytime soon, and I'm not interested in getting spammed for no reason.
,
Apr 13, 2011
@41 me too.
,
Apr 13, 2011
@41 So will I. Getting multiple emails with "yes" and "please" is pretty annoying.
,
Apr 13, 2011
Same
,
Apr 13, 2011
yeh me too, maybe others who do so could not respond with a message, so save everyone from getting another annyoing email ;) sorry!
,
Apr 13, 2011
You're making it worse! (and now I'm making it worse ...)
,
Apr 13, 2011
The whole bleeding heart thing here about 44 posts over a year and a half is pretty great entertainment. If it's so disturbing to these people why did they not setup a filter in their email client or contact the OP to see if he can modify his post to instruct people to star only. The first decent comment about starring only is 30 posts into this thread at which point most people have stopped reading. This is the only subject I've ever stared on Google code and I assume there are many who starred it that are in the same shoes as me but didn't see comment # 30. I sincerely apologize on their behalf for not being an elitist here at google code. Oh, and the hypocrisy of those bleeding hearts posting their unsubscribe notices that outnumber the recent people supporting it is like 4chan gold.
,
Apr 13, 2011
-------------------------------- READ THIS BEFORE COMMENTING: DON'T COMMENT, FFS! --------------------------------
,
Apr 13, 2011
Enough. Star or no star, comment or no comment -- this system of advocating for a change is clearly broken. This issue was opened August 25, 2009. It is the third most "starred" issue in the project. In the last year and a half, 699 people have starred the issue and suffered through bouts of crap like this morning (which I am now contributing to) as a result, because our interest in having this library added to the API is that high. Has there been a single reply from anyone at Google responsible for this code base? You know, maybe something like: * "We are definitely considering adding this library in a future release of our API." * "We will not be adding this library to our API, because..." * "In order for us to consider adding a library to our API, that library must meet the following conditions..." Anything at all would be helpful. I could never imagine letting an issue in any project I manage (open source or not) go unanswered for this long without some kind of acknowledgement at a minimum. It's borderline irresponsible that Google is continuing to do so. In the meantime, I too am joining the unstar brigade. Maybe this will attract enough attention to at least warrant a *response* from someone, if not actual action.
,
Apr 13, 2011
(No comment was entered for this change.)
Labels: Restrict-AddIssueComment-Commit
,
Apr 13, 2011
Hi Guys, Sorry about all the emails from folks unfamiliar with bug tracker etiquette; IMO it's a design flaw in the google code issue tracker, and it's being addressed separately. :) I've added a handy flag to this issue which means you can't comment on it anymore. Sorry, but I think most of you appreciate it. As for this issue in particular... I'm actually the lead developer of Modernizr (hi!)... *and* I work at Google *and* assist with our hosted libraries in my 20% time. So anyway you can imagine, I want this done even more than you guys do. :) In order for us to consider adding a library to our API, that library must ... (thanks comment 49!)... basically get tens of millions of loads per day across millions of websites. Due to the details of how browser caches work, hosting on our CDN really only benefits the web for libraries that are literally all over the place. So at the moment, the best chance Modernizr has of landing on the Google CDN is if Modernizr is being used widely across the web. We can't make any promises about definitely adding it, but you can be sure I'm very aware of the demand to do so. :) I'll update the ticket here when we have any additional news on this one. If you have any more thoughts, feel free to holler at me on twitter: @paul_irish But for now, I appreciate everyone who has starred the issue and let us know you want it. Thanks! |
|
| ► Sign in to add a comment |