1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
[8/4/14, 1:29:59 PM] Mathew Marquis: https://responsiveimagescg.github.io/eq-usecases
[8/4/14, 1:33:41 PM] Mathew Marquis: http://discourse.specifiction.org/
[8/4/14, 1:36:24 PM] Mathew Marquis: https://twitter.com/zcorpan
[8/4/14, 1:37:01 PM] Mathew Marquis: https://twitter.com/marcosc
https://github.com/ResponsiveImagesCG/newsletters
So the genisus of this article was another article I did on the 25th anniversary of the web and how much web development has changed over the eyars. We moved from sort of the web developer as someone who knew how to make IE behave to a world where developers are proposing, developing and even crowdfunding a new html element into existence.
I think if we went back even just ten years and told that story about the future of web development, no one would believe you.
So I wanted to tell the story of picture and the people who made it happen. So maybe we could start with how you came to be involved in the development of the picture element.
Boston globe site
Bruce Lawson. 2007 independently eloved name
Who set up the community group?
simon peters at opera proposed that, instead of a new element to handle images, picture wrap around img community effort from irc.
timeline:
* first picture element proposal without srcset
* very rough proposal on the mailing list
* Shot down on the mailing list when...
* community group starts
* that got shot down with the suggestion that developers create a community group, which they do.
* Apple introduces srcset for img (Mozilla rejects that idea, Chrome says sure, but doesn't do anything)
* tab atkins hybrid src-n proposal is independent of everything source ordering of attributes "grotesque" commment.
* major re-write for picture (Webkit has killed src-n, Firefox killed srcset)
* 3rd version makes it easier to implement
* adds the variant of src-n choosing syntax.
* becomes a wrapper for img
* Weiss raises money to implement pic element in Chrome
* Dust settles a bit and the picture proposal becomes an official draft at W3C
biggest community group 350
we're kind of pirate radio HTML WG.
Client hints, can't get viewport information or respond to any changes client side.
Yoav Wiess is one of 30 only non-chrome committer.
tab atkins, Simon peters opera. came up with picture element as a controller. imarcos caceros
Ian's comments:
> Some likely elements to success:
>
> - Strong sentiment in the community of the value of such feature, and effective
> communication by the proponents about the value.
> - Effective community building by Mat and others. This would include
> bringing people into the Responsive Images CG, as well as engaging
> with the HTML Working Group and getting interest from a lot of organizations.
> - Tenacity, including engaging with browser vendors and working for a consensus
> solution.
>
> The topic sort of went viral. I don't know the formula for that, but my guess is that the above elements were necessary.
But it has indeed been solved and it happened because a small group of people, none of whom had ever written a web standard before, made it happen.
They went from frustrated developers trying to solve a problem, to standards authors to browser makers. Along the way they created what's now know as the picture element, convinced the World Wide Web Consortium (W3C) to add it to the HTML5 specification and then helped raise the money to get it implemented in Google Chrome.
By the end of the year Picture will work in both Chrome and Firefox.
|
