It is the true teacher who leaves the class knowing they have learned the most.
Tucson, AZ
Joined September 2006
- Tweets 64,757
- Following 13,801
- Followers 26,057
- Likes 36,165
Well they decided to move forward with ie7 and Implement as much CSS improve JavaScript and prove the document object model and the only thing really missing at that point was offering consistent mime types to serve XML as an application which has benefits and challenges still.
1
Many people were writing books doing talks Outreach education these were developers and designers not necessarily people working on specifications at the w3c as was their Charter or Microsoft except for the web platform fellows often at the w3c like Marcus mielke and Chris Wilson
1
We spoke at a conference before the big Nick's conferences I believe where we gave perspectives on things that could be done together to get better Harmony and improve life for everyone bye bringing especially now CSS features forward. Advocacy across the world opened windows;-)
1
1
One of those task forces was myself, the Visionary JavaScript developer Dean Edwards who had actually used Microsoft Technology and JavaScript to implement settings with one script call which he humorously referred to as i e 7. Microsoft invited myself @meyerweb others to come
1
Robert scoble and other people from the Microsoft environment began to listen and open up and thus began a shift along with the wonderful Chris Wilson who had been hanging in there through all of this through the web standards project 2 over 40 members with different task forces.
1
1
The web standards project shifted perspective as Jeffrey wanted to go back to design and other projects so myself and Steve Champeon stepped into the coal lead of the web standards project he worked on the technology and kept us moving forward well I went on a lot of ranting LOL
1
1
A better open source rendering engine that eventually did become adopted by the major browsers we use now that's solved a lot of problems. The w3c began to modularize CSS which was a wonderful move because it meant implementations to be done in Cycles longer than years at a time.
1
It's important to remember we did not have the near browser monoculture we have today back then. Internet Explorer, Mozilla, Opera, Safari where at different implementations and doing different things in their rendering. Safari and open source projects especially allowed for
1
1
To Microsoft's credit that a browser they made and stopped innovating on 5 years in Internet years which is what a blink of an eye had implemented some very cool things otherwise. But issues like Box model, Dom, emerging CSS options caused us nightmares.
1
1
At that point Internet Explorer 6 owned the dominant space of the web. But Netscape still was important because it was being used all over especially in government and education and we had to write for both so now came the hacks and the workarounds as well as browser advocacy.
1
1
A new time was emerging. We had strong markup and better ideas about content pause. CSS was starting to mature so we had more options there and we were getting more skilled with how we used JavaScript but kept the content open for accessibility. But there was one big problem.
1
More rigorous markups and creative CSS began to allow for more JavaScript to be used industry evangelist such as Jeremy Keith and others really began to think you know we want to do all this but we don't want to obfuscate content we want JavaScript to be unobtrusive
1
As we were doing this work at the w3c was moving more into the XML space. The existential markup language is another Meadow language from which applications and subsets are made came out of us Gmail but with far more rigor still Proverbs but better markup this became xhtml. So
1
We saw a lot of mish-mosh from tools from developers using mixtures of CSS presentational HTML like font and colors and overwhelmingly difficult tables in order to achieve layouts along with JavaScript in competing browsers it became so overwhelming if you kids today knew haha
2
2
We had to figure out how to get what was come to known as Dynamic HTML or dhtml work with internet Explorer's development and the Netscape layer element. It was a brutal time because people were coming up with really cool things accessibility not so much but innovation yes.
1
Internet Explorer implemented the div element for division but Netscape didn't follow along and made up its own alternative known as layer. We had one API which was the document object model which makes sense in a document based web. But we couldn't really move together easily.
1
So in the next few years right around 97-98 we had some CSS we had HTML with a lot of table base layouts and spacer GIFs and we had some JavaScript we had two competing browsers Netscape and Internet Explorer each of whom ended up adopting elements that challenged us so much.
1
1
If those folks new to web development don't remember the days of JavaScript is being a toy to play with it's come a long way baby when we look at ecma 6 we see a real growth from the days where we used it for non-essential behavior and style remember geocities lol!
1
2