- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 17 Jun 2009 09:42:54 -0500
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: www-style@w3.org
On Wed, Jun 17, 2009 at 1:31 AM, fantasai<fantasai.lists@inkedblade.net> wrote: > Abandoned Working Drafts > ------------------------ > > Scribe: alexmog > discussing mathml > RESOLVED: css math -- dropped > anne: what does dropping mean? > daniel: another group takes over > > CSS style Attribute syntax 3 > chris: scoping is still needed? > discusing scope, how it is related to HTML5 > anne: HTML5 allows more, media independent style sheets, etc. > david: suggest dropping this spec but publish what needs to be > specified elsewhere > RESOLVED: drop "style attribute syntax" spec > RESOLVED: keep "style attribute syntax" spec, remove extensions, > only keep current syntax > ACTION: fantasai: edit "style attribute syntax" to constrain to current > syntax > > CSS Hyperlink Presentation Module > daniel: reason for the spec is to allow to overide link behavior > from user style sheet > the behavior is now available via DOM > browser vendors don't express interest in implementing it > RESOLVED: drop Hyperlink Presentation module > > CSS Web Fonts Level 3 > merged with CSS3 Fonts -- links should be redirected to the merged spec > > CSS Introduction > RESOLVED: snapshot will override; when snapshot is published, > introduction link will point to the snapshot > > CSS Reader Media type > already dropped, should not be in current work > RESOLVED: publish a note on not working on CSS Reader Media Type > > CSS OM View > Anne is working on the spec, it is meant to obsolete DOM spec > status -- in WD for over the year > anne: time to publish a new WD > RESOLVED: publish a new working draft on CSS OM View > anne: have requests for support of 3D transforms > > RESOLVED: Aural stylesheets - dropped > > CSS Lists > fantasai: should not be dropped > > CSS Scoping > daniel is the editor > daniel: the idea was to suggest a way to scope stylesheets to an > element; HTML5 has scoping support, this spec is not needed > RESOLVED: CSS Scoping is droppped > > CSS Ruby > IE has partial implementation > ACTION: Arron to send a list of CSS Ruby properties supported by IE8 > RESOLVED: Ruby spec is on hold until an editor is found > > CSS Object Model > no working draft yet > anne: huge project, no time currently > RESOLVED: CSS Object Model -- not dropped, abandoned for the time being > > CSS Presentation Levels > Hakon: let's drop it. it's going nowhere. > RESOLVED: CSS Presentation Level -- not being worked on for undetermined > time > discuss the difference between dropped, abandoned and on hold > discussing keeping documents on low-priority, off-charter list vs. > completely removing documents and saying we are not working on it any > more > RESOLVED: CSS Presentation Level -- discontinue, publish a note > that contains the whole content of current document I'm happy with the decisions on these modules. I sort of liked presentation levels, but don't have a problem with removing it - it seems like it was adding significant behavior to CSS, which can be handled better in JS. ~TJ
Received on Wednesday, 17 June 2009 14:43:45 UTC