Comments on: Apple’s Web Inventions http://www.codedread.com/blog/archives/2008/04/25/apples-web-inventions/ Sun, 07 Mar 2010 07:18:03 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Jeff Schiller http://www.codedread.com/blog/archives/2008/04/25/apples-web-inventions/comment-page-1/#comment-1026 Jeff Schiller Tue, 29 Apr 2008 22:41:07 +0000 http://blog.codedread.com/archives/2008/04/25/apples-web-inventions/#comment-1026 Update: Added bit about <a href="http://webkit.org/blog/182/css-reflections/" rel="nofollow">CSS Reflections</a> Update: Added bit about CSS Reflections

]]> By: mabdul http://www.codedread.com/blog/archives/2008/04/25/apples-web-inventions/comment-page-1/#comment-1025 mabdul Sat, 26 Apr 2008 11:32:51 +0000 http://blog.codedread.com/archives/2008/04/25/apples-web-inventions/#comment-1025 iCab 4 and Epiphany will use also webkit in future iCab 4 and Epiphany will use also webkit in future

]]> By: Maciej Stachowiak http://www.codedread.com/blog/archives/2008/04/25/apples-web-inventions/comment-page-1/#comment-1024 Maciej Stachowiak Sat, 26 Apr 2008 08:44:23 +0000 http://blog.codedread.com/archives/2008/04/25/apples-web-inventions/#comment-1024 We have already proposed many of the big ticket CSS items you mention as new CSS Modules. I would expect most of the others to be proposed more formally in due course as well. In the area of CSS, we like to come with a preliminary implementation because it is often difficult to argue the benefit of new features in the abstract. An implementation that can be experimented with is often much more compelling and informative about details of the design. Another long-ago WebKit innovation is and the placeholder attribute for elements. We have proposed both of these for HTML5, although forms work on HTML5 is currently on hold. Many of our recent new features in the areas of HTML and general Web APIs don't make your list because we started with standards for those in mnay cases. For example, we were significant contributors to the design of the and elements, the SQL Storage API, and Offline App support, but these ended up in the HTML5 spec before we implemented. We've also added features such as postMessage, getElementsByClassName and querySelector that came straight out of HTML5 or Web API WG specs. In general, our desire is to see the web improve as a platform and to bring these features to standards and encourage other browsers to adopt them. We have already proposed many of the big ticket CSS items you mention as new CSS Modules. I would expect most of the others to be proposed more formally in due course as well. In the area of CSS, we like to come with a preliminary implementation because it is often difficult to argue the benefit of new features in the abstract. An implementation that can be experimented with is often much more compelling and informative about details of the design.

Another long-ago WebKit innovation is and the placeholder attribute for elements. We have proposed both of these for HTML5, although forms work on HTML5 is currently on hold. Many of our recent new features in the areas of HTML and general Web APIs don’t make your list because we started with standards for those in mnay cases. For example, we were significant contributors to the design of the and elements, the SQL Storage API, and Offline App support, but these ended up in the HTML5 spec before we implemented. We’ve also added features such as postMessage, getElementsByClassName and querySelector that came straight out of HTML5 or Web API WG specs.

In general, our desire is to see the web improve as a platform and to bring these features to standards and encourage other browsers to adopt them.

]]> By: Jeff Schiller http://www.codedread.com/blog/archives/2008/04/25/apples-web-inventions/comment-page-1/#comment-1023 Jeff Schiller Sat, 26 Apr 2008 04:15:17 +0000 http://blog.codedread.com/archives/2008/04/25/apples-web-inventions/#comment-1023 @Mark. Thanks very much for those links, I have done some updates to my blog post. One recommendation: Perhaps the Safari blog entries could be updated with the spec proposals so that goofs like me don't go shooting off my mouth? ;) @Mark. Thanks very much for those links, I have done some updates to my blog post. One recommendation: Perhaps the Safari blog entries could be updated with the spec proposals so that goofs like me don’t go shooting off my mouth? ;)

]]> By: Bob http://www.codedread.com/blog/archives/2008/04/25/apples-web-inventions/comment-page-1/#comment-1022 Bob Sat, 26 Apr 2008 03:54:55 +0000 http://blog.codedread.com/archives/2008/04/25/apples-web-inventions/#comment-1022 Last I checked, MacOS was retired years ago in favor of Mac OS X. Last I checked, MacOS was retired years ago in favor of Mac OS X.

]]> By: Mark Rowe http://www.codedread.com/blog/archives/2008/04/25/apples-web-inventions/comment-page-1/#comment-1021 Mark Rowe Sat, 26 Apr 2008 02:49:09 +0000 http://blog.codedread.com/archives/2008/04/25/apples-web-inventions/#comment-1021 Several of the CSS features you mention have already been proposed for standardisation: see http://lists.w3.org/Archives/Public/www-style/2008Apr/0208.html for instance. The background-position-x/background-position-y properties have also been discussed: see http://www.w3.org/Style/CSS/Tracker/issues/9 . Other properties, such as rtl-ordering and text-security, exist primarily for use within the engine to emulate behaviour of the system widgets that WebKit itself implements in terms of HTML (password fields, buttons, etc). Mozilla has a long list of extensions for a similar reason ( http://developer.mozilla.org/en/docs/CSS_Reference:Mozilla_Extensions ). Several of the CSS features you mention have already been proposed for standardisation: see http://lists.w3.org/Archives/Public/www-style/2008Apr/0208.html for instance. The background-position-x/background-position-y properties have also been discussed: see http://www.w3.org/Style/CSS/Tracker/issues/9 . Other properties, such as rtl-ordering and text-security, exist primarily for use within the engine to emulate behaviour of the system widgets that WebKit itself implements in terms of HTML (password fields, buttons, etc). Mozilla has a long list of extensions for a similar reason ( http://developer.mozilla.org/en/docs/CSS_Reference:Mozilla_Extensions ).

]]>