[WSG] CSS2.1 now an official recommendation
Hello, I can barely believe that CSS2.1 has only just become an official recommendation (see http://www.css3.info/css2-1-and-the-css3-color-module-become-official-w3c-recommendations/). Could anyone explain why this took so long? Many of us are already using CSS3! Seems to me that speeding the process of approval along (just a little) might encourage browser vendors to comply with web standards ... Insights would be appreciated. Kind regards, Grant Bailey *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] CSS2.1 now an official recommendation
On 6/17/2011 6:03 PM, Grant Bailey wrote: Hello, I can barely believe that CSS2.1 has only just become an official recommendation (see http://www.css3.info/css2-1-and-the-css3-color-module-become-official-w3c-recommendations/). Could anyone explain why this took so long? Many of us are already using CSS3! Seems to me that speeding the process of approval along (just a little) might encourage browser vendors to comply with web standards ... Insights would be appreciated. Kind regards, Grant Bailey This all has to do with the large corporates on the W3C working groups. Microsoft as well as IBM and others all have representation. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] CSS2.1 now an official recommendation
Does your amplifier go up to 11? On Fri, June 17, 2011 9:03 am, Grant Bailey wrote: Hello, I can barely believe that CSS2.1 has only just become an official recommendation (see http://www.css3.info/css2-1-and-the-css3-color-module-become-official-w3c-recommendations/). Could anyone explain why this took so long? Many of us are already using CSS3! Seems to me that speeding the process of approval along (just a little) might encourage browser vendors to comply with web standards ... Insights would be appreciated. Kind regards, Grant Bailey *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] IE issues: display none vs absolute position for show/hide effect
David, Thanks! On Jun 16, 2011, at 9:47 AM, David Hucklesby wrote: But that's the reason it shows up momentarily on slow connections. I suspect it only shows in IE due to longer latency in those old browsers - JavaScript takes a whole bunch longer to kick in. Using jQuery hide comes too late in those browsers. Which is precisely the problem that the solution I offered is designed to address. Well, I didn't know this because the is the first time I face this issue and yet i have used 'hide' very often. So I didn't really understand why you suggested to use extra JS in the head section and use display none (something I really wanted to avoid) until you explained it . Some folks sure are stubborn! ;) Stubborn is a must quality you need to survive in the dog eats dog jungle if you haven't already knew that :-) -- Cordially, David *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
