Skip to content
This repository has been archived by the owner on Aug 5, 2020. It is now read-only.

Use of a real picture element can create compatibility issues #210

Open
yoavweiss opened this issue Oct 24, 2013 · 3 comments
Open

Use of a real picture element can create compatibility issues #210

yoavweiss opened this issue Oct 24, 2013 · 3 comments

Comments

@yoavweiss
Copy link

Since the picture proposal is still a draft, and future changes to it are highly probable, adding it to the markup can actually be harmful to the standardization process and can create future compatibility issues.

A different pattern (such as picturefill’s use of spans with a “data-picture” attribute) is highly preferred, since it enables Web developers to experiment with a picture-like syntax, without the possible compatibility issues.

Would it be possible to avoid the use of picture and switch to a similar pattern instead?

@jansepar
Copy link
Contributor

Yep this is definitely a valid issue. Will address it ASAP!

@jansepar
Copy link
Contributor

jansepar commented Dec 2, 2013

Hi @yoavweiss, I've issues a pull request for this, would love if you want to take a quick peek to see if I've done it as you were hoping. I've actually made it so that <picture> still works for backwards compatibility, but I've changed all example code and examples on the website to use <span data-picture>. Let me know if this change is to your liking!

@yoavweiss
Copy link
Author

Hi @jansepar !
As long as the use of explicit is discouraged, I'm cool with this change. (backward compat is not a problem, as long as new sites don't use the explicit ).

Thanks! :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants