Changes

Jump to: navigation, search

Tantek-Mozilla-Projects

279 bytes added, 01:49, 8 July 2011
remaining tasks: update and minimize tasks necessary to complete before pubishing another CSS3-UI LCWD
Remaining tasks to get CSS3 UI to PR:
* add ''ime-mode'' per Mozilla definitions
** https://developer.mozilla.org/en/CSS/ime-mode
** It is implemented unprefixed in FF3+ and WinIE5+
* add ''box-sizing: padding-box'' per Mozilla definitions
* '''text-overflow'''
** clarify text per emails from fantasai/RoC or consider explicitly stating as undefined (per suggestions from RoC)
*** interaction of text-overflow:ellipsis with event handling
** also create an implementer FAQ on the CSS WG wiki re: text-overflow accordingly
* update ''appearance'' property with updated set of native UI controls from Alex Faaborg.
* '''resolve issues'''. resolve/apply proposals from issues list: http://wiki.csswg.org/spec/css3-ui
* add ''ime-mode'' per Mozilla definitions
** https://developer.mozilla.org/en/CSS/ime-mode
** It is implemented unprefixed in FF3+ and WinIE5+
* publish new CSS3 UI LCWD editors draft with new at-risk features based on above implementation evidence (or imminent implementation - kept at risk), and all known outstanding issues resolved. (back to last call because we added features after the CR, and moved some previous features to at-risk). * '''implementation documentation'''. document claims of existing implementations (CSSWG implementers have until 2010-09-17 to submit claims of implementation)
** Webkit CSS3 UI - http://lists.w3.org/Archives/Public/public-html/2009Sep/0060.html
** Opera CSS3 UI - http://lists.w3.org/Archives/Public/public-html/2009Sep/0202.html
* document actual implementation results
* reducing feature set down to what's been implemented in more than one browser** write new CSS3 UI LCWD editors draft with only non-at-risk features based on above implementation evidence (or imminent implementation - kept at risk)** write new UI Selectors FPWD editors draft with all new UI selectors (consider limiting to those with at least one implementation, any with less than 2 implementations, mark at risk up front) 
* collect/address new CSS3 UI LCWD issues as they are reported
** respond to all the commenters on issues with proposed resolutions (hopefully thus addressing their concerns and resolving the issues accordingly)
* edit CSS3-UI CR draft accordingly that is ready for PR
** reduce feature set down to what's been implemented in more than one browser, or in one browser and imminently expected in another browser.
* WG processes for taking it to PR
Canmove, confirm
2,679
edits

Navigation menu