responsiveimagescg / responsiveimages.org Goto Github PK

@anselmh see your author information on the demos page "on a grid system". can you please change it!
Demos overview page looks fine ;-)

cheerio

See ResponsiveImagesCG/picture-refimp#10 (comment)

Maintaining multiple sites is causing us issues, so demos should be hosted on the dream host server and the we should create a header template.

Needs a rewrite. Pinged Shane to help fix!

Looking like the HTTPS thing again, @marcoscaceres.

Need a new header image. Need to remove the old one from the demo site.

@yoavweiss said:

Can we add https://w3c.github.io/webappsec/specs/upgrade/ to make sure this doesn't happen again with some other resources? (in supporting browsers)

And I believe we can :)

Actually Chrome tries to get images on http://demos.responsiveimages.org/img/devices-sm.gif where the images are not present

We should add the new (white/grey) pattern to the Twitter page background, and if we're going to keep that new header style, it'd be great to try a dark grey version underneath the avatar and white text.

This topic involves a deep level of understanding about how browsers--and indeed, the standards process--works. An FAQ would provide a single link that could be shared whenever this topic arrises on social networks or blogs, or form the basis discussion in this area (i.e. any article written about this topic would be able to link to and/or reference this document to give readers a basic understanding of the issues) before continuing.

For those wishing to know more about the work of the group, and the reasoning behind the two proposals, this page could answer common questions about how these patterns were arrived at. It could also explain why certain perceived solutions won't work, or how they might provide sub-optimal experiences for users.

Need to gather and add links to the prollyfills for each spec to the site.

We should encrypt the site

The website is currently missing links to the following:

• All CG work items: http://bugs.responsiveimages.org
• IRC Logs: http://ircbot.responsiveimages.org
• mailing list: http://list.responsiveimages.org
• W3C CG: http://w3c.responsiveimages.org
• demos http://demos.responsiveimages.org
• downloads http://downloads.responsiveimages.org

The last one is there, but would be nice to have all the links in the footer.

See: https://twitter.com/gregwhitworth/status/456912833217708033

The main website needs a page to show off the logos. Kinda like the artwork page for Apache Cordova.

It would be great if we had a way of adding articles/blog posts to the website - we have some of the greatest minds in the world on the subject in the CG, so it would be a shame to not tap into that resource. It would make the site a valuable resource to developers (both inside the RICG and outside)... it gives people a reason to return to the site and to link to the site.

Would like us to initially discuss what members think, and what infrastructure to allow us to make that happen.

It looks like the issue list on responsiveimages.org isn’t updating anymore; could someone have a look at that?

Currently, the twitter button opens up a twitter box instead of the twitter account page where people can follow us. This is a bit annoying, tbh. I often go looking for the link to our twitter page on our homepage and can't find it :(

It appears to be a bit behind the times.

With @yoavweiss landing support for media queries in his picture implementation in Chromium, we can probably start considering promoting the chromium build on the website.... "play with the future, today!" :)

You may want to change your message on your facebook icon.
When sharing your site on facebook it says:

"DreamHost
http://responsiveimages.org/
The DreamHost customer who owns responsiveimages.org has not yet uploaded their website or has chosen to leave this holding page active."

Cheers,
Annett

The site should link to our demo page: http://demos.responsiveimages.org.

Manually having to push the site to dreamhost is no fun. It would be really nice if Travis.ci could just ftp all the changes up.

The use cases document (http://usecases.responsiveimages.org) is written using a style and tone aimed at browser vendors and others with deep knowledge of the subject.

While this document is useful for that audience, there is a second audience of designers and developers who would be better served by having more approachable content available to them.

A page or section on the responsiveimages.org site should explain the use cases in plain English. This could point to (further) examples where these use cases exist already in the wild, noting perhaps how such implementations result in users having to download unnecessary data than is required (for example).

If people wishing to get involved with RICG need to understand the use cases (why they matter, where they've arisen from, how they can't be addressed using current markup etc.), it is important that this information is available in an easy to understand and accessible format.

Can we add a favicon.ico to this project. I created one with the relevant imagery:
http://christianoliff.com/responsive/favicon.ico

I tried to make a pull request for this but didn't have access.

If you click the very top pixel of a hyperlink, nothing happens.

Screencast: http://cl.ly/2a1h1q1U442v

I've encountered this issue before in personal work. It's because the click target on mousedown is not the same as the click target on mouseup due to the 1px down shift when you're hovered on the very top edge of the link. Spec says mousedown and mouseup target have to be the same.

We need a landing page with links and info about who we are, what we do, what we are working on, and how people can get involved.

And God only knows what other URLs.

The HTTPS transition for responsiveimages.org has been way more trouble than it’s worth, considering that it is almost entirely redirects and a few static pages with no data that needs securing. If we can’t get this sorted out in a reliable way, I’m not sure what the benefit is compared to the cost.

In demos.responsiveimages.org first line is :

<?php include_once( "issues.php" ); ?><!doctype html>

php tag is not parsed/rendered.

The demos on the demos page use Picturefill so Yoav's Chromium build is not actually required.
If I'm not missing something the following could be changed.

This requires you have the working Chromium build by Yoav Weiss you can download here. Instructions are on the demo pages.

to something like:

This is optimally viewed with the working Chromium build by Yoav Weiss you can download here. Instructions are on the demo pages.

If there's no objection, I can send a pull request with the change.

Links on the site are currently not underlined. This may cause accessibility issues.

I've recognized it is nowhere mentioned who is involved into the RI development actively. Should we add a list of contributors? We could do this via CONTRIBUTORS.md just in repo or also on the website itself as a list.

I would vote for it though have no preference how to do this. Would love to hear your thoughts…

It would be nice if the logo on our site was responsive. Or that we had a nice example of a responsive image.

The logo download link is broken if you click on it from the demos page. See pull request #59 for fix.

Front page says:

"The demos on this page require that you have our Chromium build."

Should probably say something like:

"The demos on this page work in any modern browser, but if you want to see the real deal (tm) grab our Chromium build."

At least one user will be forced to wait the 2 seconds for the data to download - and, in addition, the data will always be at risk of being stale. This is a bit backwards, what we need to do is get Github to ping our server when an issue changes (PubSubHubbub-style - supported by Github). That is trivial to do on Github using one of the github services (I'll file a separate bug for that). Then we just need a refreshissues.php on the server as an end point.

This also soves the credentials on server issue, as the number of requests made per day will be way under 100.

Site is not scaling properly in iOS 7. It overflows on the right.

Old https://github.com/ResponsiveImagesCG/responsiveimages.org/blob/master/js/picturefill.js is old

The demos should show both <picture> and srcset and work accordingly with the right prollyfill.

Shouldn't we add .editorconfig and .gitattributes to all of our repositories for a consistent workflow and to avoid line-break issues etc?

It might make sense to include buttons on the website where users are sent to the bugs that are filed at the user agents with a notice to vote for implementation.
This not only helps pushing it forward by votes but also users can view the current implementation status this way.

I'd love to hear some feedback on this.

(was Remove srcset example in favor or src-n)

We should feature the other competing solutions too. That is

• src-n
• client-hints

it would be nice to show people what's going on, be that by pulling in the ricg twitter feed, or a blog, or whatever.

As of today, example pictures are broken.
HTTP answer is 410 Gone for all images on http://respimg.cdnconnect.com/

When accessing the site via HTTPS, browsers block the CSS, scripts, partially images away as it’s served via HTTP. Reason is probably the Google mod_pagespeed optimizer messing up with the protocols.

Can someone fix this on the server, @marcoscaceres @Wilto?

We should link to http://picture.responsiveimages.org/#relationship-to-srcset instead.

Currently a Google search for "responsive images" brings up responsiveimages.org near the top (2nd result on an incognito windows for me). That's great; but the chances are that someone searching for those terms are looking for information on how to use responsive images, not on the intricacies of the spec.

I suggest that the links under "Where can I learn more" are replaced with links to resources on how to use responsive images instead. There are plenty of great resources that have been mentioned on the newsletter. Here are a few suggestions:

• http://blog.cloudfour.com/responsive-images-101-definitions/
• http://www.danmatthew.co.uk/2015/04/19/implementing-responsive-images/
• https://scottjehl.github.io/picturefill/
• http://www.fivesimplesteps.com/products/practical-responsive-images

@baamenabar, the "No FOLRI on reorientation" seems to have broken, so I'm disabling it. When you have a chance, can you take a look?