Canmove, confirm
2,678
edits
Changes
Web We Want lead, AB, drop old store links, https, Internet Archive links for dead sites, a few opportunistic archive additions
* [[Standards]] Mozilla point of contact:
** [[W3C]] Advisory Committee (AC)
** [https://webwewant.fyi/about/ Web We Want] lead
** [[WHATWG]] Steering Group (SG)
* [[Standards]] projects/groups
** [https://www.w3.org/wiki/AB W3C Advisory Board (AB)]*** [https://github.com/w3c/AB-public/tree/main/Vision W3C Vision]([https://github.com/w3c/AB-public/issues issues]), ** [[CSS]] WG, OpenUI, Process CG
* [https://indieweb.org/ IndieWeb community for independent websites]
== To be updated ==
----
'''The rest of this page needs a major update.''' - [[User:Tantek|Tantek]] ([httphttps://tantek.com/ tantek.com]) 15:53, 3 July 2017 (PDT)
Previously from [[Tantek]]:
=== APNG adoption ===
See: [[APNG]]
== Critical areas of focus ==
* '''<span class="p-category category">[[IndieWebCamp|IndieWeb]]</span>''' - the independent web, providing user-centered freedom, ownership, and control over and above silos and their <abbr title="terms of service">TOSes</abbr>es.
* '''<span class="p-category category">[[Microformats]]</span>''' - open standards for marking up information in HTML, simpler, easier, more maintainable, and higher quality than alternatives (RDFa, microdata), and sidefile efforts (XML, RDF). See also <span class="p-category category">[[HTML5]]</span> and Tantek's [httphttps://tantek.com/html5now book on getting started with HTML5].
** '''[[microformats2-parsing]]''' in particular landing support in Firefox Toolkit/Platform for Share, Social Bookmarking, Context Menu, Shopping
* <span class="p-category category">[[Tantek-Mozilla-Projects#CSS3_UI|CSS3-UI]]</span> (editor, and contributing to <span class="p-category category">[[CSS3]]</span> in general)
* <span class="p-category category">[[#HTML5|HTML5]]</span> (contributing)
* <span class="p-category category">[[microformats2]]</span> editor of, including [httphttps://microformats.org/wiki/microformats2-parsing microformats2 parsing spec], <span class="p-category category">[[hCard]]</span>, <span class="p-category category">[[hCalendar]]</span>, and other vocabularies.* <span class="p-category category">[[IndieWebCamp]]</span> specifications for independent web publishing and peer to peer interactions: [httphttps://indiewebcampindieweb.comorg/authorship authorship], [httphttps://indiewebcampindieweb.comorg/vouch vouch], [httphttps://indiewebcampindieweb.comorg/web-sign-in web-sign-in], and contributor to [httphttps://indiewebcampindieweb.comorg/webmention webmention]
* Helping out with [https://compat.spec.whatwg.org/ Compatibility] spec ([https://github.com/whatwg/compat/ github src]).
Additional projects:
* [[Events]]: IndieWebCamp, [httphttps://indiewebcampindieweb.comorg/Homebrew_Website_Club Homebrew Website Club], W3C TPAC and WG [[standards]] meetings
* <span class="p-category category">[[WebActions]]</span>
* <span class="p-category category">[[Mozillians]]</span> ([[Mozillians/Phonebook|Phonebook]], [[Mozillians/Events_Manager|Events Manager]])
----
The rest of this page needs a major update. - [[User:Tantek|Tantek]] ([httphttps://tantek.com/ tantek.com]) 20:04, 27 May 2016 (PDT)
----
* [[Standards]] groups/community participation
** W3C: SocialWG, CSSWG, AB, HTMLWG, TPAC, FSW
*** [httphttps://www.w3.org/wiki/SpecProd/Restyle Restyle W3C: Towards a More Usable Spec Template]
** IETF: VCARDDAV (vCard4)
** Community: IndieWeb, microformats, OWF, WHATWG, Portable Contacts, OpenID, OAuth(2)/xAuth, RelMeAuth, Activity Streams
Needs review (the following projects need review to determine updated next steps and reprioritize)
* CSSWG charter: httphttps://wiki.csswg.org/planning#charter-2011
* [[Tantek-Mozilla-projects#CSS_Style_Attributes|CSS Style Attributes]]: Achieved CR. Next action: test suite to help exit CR.
* [[Tantek-Mozilla-projects#CSS3_Color|CSS3 Color]]: Achieved REC, gathering editorial issues for 2nd edition.
Inbox (add stuff here) :
* Review httphttps://dev.w3.org/csswg/css-module/Overview.src.html
* ... add more suggestions here
As a foundational technology, everything else (microformats, CSS3, WebApps, etc.) depend on getting [[HTML5]] right, and fixing problems in the <span id="HTML5_spec_improvements">HTML5 spec</span>.
* <code><time></code> element - from [httphttps://www.w3.org/wiki/User:Tantekelik#time_element_issues W3C wiki: time element issues]. Just need to keep a watch on these issues in the HTMLWG telcons, [httphttps://lists.w3.org/Archives/Public/public-html/ list], [http://krijnhoetmer.nl/irc-logs/html-wg/ irc] and make sure the proposals are accepted (if not already), spec changes made (if not already), and issues closed accordingly.** [httphttps://www.w3.org/html/wg/tracker/issues/183 Issue 183]: [httphttps://www.w3.org/wiki/User:Tantekelik/time_element <time> element change proposal] (developed on wikimo: [[HTML5/time#expand_time|HTML5/time]])*** [httphttps://dev.w3.org/html5/spec/the-time-element.html#the-time-element incorporated in spec], awaiting issue closure.** [httphttps://www.w3.org/html/wg/tracker/issues/184 Issue 184]: [httphttps://www.w3.org/wiki/User:Tantekelik/data_element <data> element change proposal]*** [httphttps://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-data-element incorporated in WHATWG spec], awaiting inclusion in W3C HTML5 spec, issue closure.** [httphttps://www.w3.org/html/wg/tracker/issues/185 Issue 185]: [httphttps://www.w3.org/wiki/User:Tantekelik/drop_pubdate drop pubdate attribute change proposal]*** [httphttps://dev.w3.org/html5/spec/the-time-element.html#the-time-element incorporated in spec] (absence of pubdate), awaiting issue closure.
=== needs re-consideration ===
The goal in this second scenario is to enable building rich native-app-like user interfaces where the path of least resistance to building it uses building blocks that in themselves enable accessibility. I think this is both possible, and is a necessary course of action to avoid having to do "bolt-on" accessibility later.
Note that providing facilities for (re)building native-app-like UIs is just one part of what such rich web-apps need to compete with native apps. See http://arewemobileyet.com/ for more on hardware access etc.
For now, the sections below focus on addressing/solving the first cluster of use cases first.
This is a big design challenge. Take a look at what Opera has done for example (in terms of challenges). Here is a simple test page which shows default renderings - compare in various browsers and try interacting with the new widgets especially in Opera:
See [[HTML5/input]] for more <input> element tests.
* ability to select specific "pieces" of any compound/composite form control for styling
** feeds into requirements for CSS pseudo-elements
** consider existing [httphttps://www.w3.org/TR/css3-ui/#pseudo-elements CSS3-UI pseudo-elements]
*** ::value can be used for selecting/styling placeholder text (see [https://bugzilla.mozilla.org/show_bug.cgi?id=457801#c25 bug 457801 comment 25])
*** ::choices can theoretically be used to style the popped-up state of a <code><select></code> pop-up menu. No known implementations.
** consider additional pseudo-elements based on web designer requests for stylability of form controls
*** <code>[[HTML5/select|<select>]]</code>
**** [httphttps://stackoverflow.com/questions/611482/change-color-and-appearance-of-drop-down-arrow color and appearance of drop down arrow]
*** <code>[[HTML5/input#type_search|<input type=search>]]</code>
**** see examples from Jonas Sicking
* ability to select specific "states" of any form control (may require ability to select states of specific pieces as well - that will be a challenge though as pseudo-elements themselves cannot have pseudo-classes in CSS)
** existing [httphttps://www.w3.org/TR/css3-selectors/#UIstates Selectors UI pseudo-classes], and some notes on [httphttps://www.w3.org/TR/html5/interactive-elements.html#pseudo-classes how HTML5 DOM property states trigger these pseudo-classes]
*** :hover :active - based on mouse/pointer interactions. the challenge here is to find alternatives for touch based interfaces.
*** :focus - an element which is currently accepting keyboard, pointer, or other input device events.
*** :checked - based on the "checked" property on input types "radio" and "checkbox", and also on the "selected" property on option element.
*** :indeterminate - based on the "indeterminate" property of the input types "radio" and "checkbox".
*** :default - [httphttps://www.w3.org/TR/html5/interactive-elements.html#selector-default default buttons or submit buttons]
*** :valid and :invalid - input elements that are candidates for constraint validation and either do or don't (respectively) satisfy their constraints.
*** :in-range and :out-of-range - input elements that are candidates for constraint validation and that are neither under nor overflowing (for :in-range) or either under/overflowing (for :out-of-range).
*** :required and :optional - [httphttps://www.w3.org/TR/html5/interactive-elements.html#selector-required see HTML5 description of being required / required attribute]*** :read-only and :read-write - [httphttps://www.w3.org/TR/html5/interactive-elements.html#selector-read-only see HTML5 description of read-only vs read-write elements].
** additional pseudo-selectors as needed for states/portions included in HTML5 forms elements features
*** "placeholder" attribute - needs a new :-moz-placeholder pseudo-class ([https://bugzilla.mozilla.org/show_bug.cgi?id=457801 bug 457801])
===== CSS UI appearance values =====
<span id="CSS3_UI_appearance_values"> </span>
From [httphttps://www.w3.org/TR/css3-ui/#appearance-val CSS3 UI 5.1. Appearance values]:
Needs:
==== CSS Style Attributes ====
;latest published draft (CR)
:httphttps://www.w3.org/TR/css-style-attr/
;latest development / in progress draft
:httphttps://dev.w3.org/csswg/css-style-attr/
;spec source (for editing)
:httphttps://dev.w3.org/csswg/css-style-attr/Overview.src.html
;test suite
:TBD
:TBD
;issues list for the current draft
:httphttps://wiki.csswg.org/spec/css-style-attr
===== remaining tasks =====
** emailed 2011-080
See also CSSWG wiki task list: httphttps://wiki.csswg.org/spec/css-style-attr
==== CSS3 UI ====
;latest published draft
:httphttps://www.w3.org/TR/css3-ui/
;latest development / in progress draft
:httphttps://dev.w3.org/csswg/css-ui/
;spec source (for editing)
:httphttps://dev.w3.org/csswg/css-ui/Overview.bs
;test suite
:httphttps://test.csswg.org/suites/css-ui-3_dev/nightly-unstable/
;implementation reports of the test suite
:TBD
;issues list for the current draft
:httphttps://wiki.csswg.org/spec/css3-ui
===== remaining tasks =====
Remaining tasks to get CSS3 UI to PR:
* '''resolve issues'''. resolve/apply proposals from issues list: httphttps://wiki.csswg.org/spec/css3-ui
* '''collect other tasks'''
** Extract CSS3-UI related tasks from "mozilla-next-actions.txt" local text document
** And add to httphttps://wiki.csswg.org/spec/css3-ui as concrete issues to resolutions and status
* '''text-overflow'''
** create an implementer FAQ on the W3C wiki re: text-overflow accordingly
* '''implementation documentation'''. document claims of existing implementations on W3C wiki
** Webkit CSS3 UI - httphttps://lists.w3.org/Archives/Public/public-html/2009Sep/0060.html
** Opera CSS3 UI
*** [https://web.archive.org/web/20160604120040/http://www.opera.com/docs/specs/presto29/css/basicuserinterface/www.opera.com/docs/specs/presto29/css/basicuserinterface] (Internet Archive link)*** httphttps://lists.w3.org/Archives/Public/public-html/2009Sep/0202.html
** Mozilla CSS3 UI
*** [https://developer.mozilla.org/en/CSS/:default :default]
***** if/when fixed, add that detail to spec
**** box-sizing prefix drop: https://bugzilla.mozilla.org/show_bug.cgi?id=243412
**** move icon support ( httphttps://www.w3.org/TR/css3-ui/#element ) to W3C wiki
***** 'icon' property
***** 'content:icon' value
==== CSS4 UI ====
* write CSS4 UI FPWD with:
** public requests recorded: httphttps://wiki.csswg.org/spec/css4-ui
*** the below items should be incorporated into that CSSWG wiki page
** previous CSS3-UI features that got dropped
**** 'user-modify'
**** 'user-select'
***** all suggested to replace 'contentEditable': [httphttps://lists.w3.org/Archives/Public/www-style/2010Dec/0371.html www-style: Implementing contentEditable in CSS3 UI]
** other CSS features that are UI related in other CSS or other W3C specs
*** [https://developer.mozilla.org/en/CSS/%3a-moz-placeholder :placeholder] pseudo-class. related: [https://bugzilla.mozilla.org/show_bug.cgi?id=457801 bug 457801]
*** '''overflow-x overflow-y'''. incorporate '''[https://developer.mozilla.org/En/CSS/Overflow-x overflow-x]''' and '''[https://developer.mozilla.org/En/CSS/Overflow-y overflow-y]'''
**** pull-in the entirety of section 16 from
***** httphttps://www.w3.org/Style/Group/css3-src/css3-box/#overflow
**** sync (incorporated) any updates/changes in 2.1:
***** httphttps://www.w3.org/Style/Group/css2-src/visufx.html#overflow
**** note examples/behaviors in Gresley's overflow tests
***** httphttps://css-class.com/test/css/overflow/block-inside-auto-width-float-overflow.htm
**** search www-style for issues related to 'overflow-x' and 'overflow-y'
***** ask Anne van Kesteren and www-style directly
**** check that css3-marquee implicitly deals with overflow-x and overflow-y correctly
***** httphttps://www.w3.org/TR/css3-marquee/#the-overflow-style
**** investigate discussion of ink overflow vs layout overflow - [[User:Fantasai|fantasai]] will get more info on this. e.g. box-shadow should never trigger scrollbars. do margins? maybe they don't trigger overflow but if there is overflow anyways (something else triggers scrollbars), then margins influence the dimensions of the scrollable area.
*** '''outline-radius''' per implementation: Mozilla supports [https://developer.mozilla.org/en/CSS/-moz-outline-radius -moz-outline-radius] (no second implementation however - thus in CSS4 UI)
*** <span id="new-resize-values">new 'resize' values</span> - e.g. '''grow-vertical''', '''grow-horizontal'''
**** Facebook uses some JS to add rows to text areas when you hit the end of the available space. It feels nicer than a scrollbar because you can see all of what you typed -- the height of the text area just grows and grows as you need it. It would be great to have 'resize' property values that allow the browser to auto-grow a textarea as a user enters data, e.g. 'grow-horizontal', 'grow-vertical'. 'grow-vertical' would emulate the current behavior that FB does with JS. (note from fantasai - this is the behavior you'd get with fixed min-height and auto height, so CSS can do this already if HTML doesn't get in the way)
**** Update 2011-032: [httphttps://twitter.com/LeaVerou/status/32642516146724866 @LeaVerou requested] "elastic textarea effect with pure CSS" [httphttps://twitter.com/LeaVerou/status/32651575688175616 and follow-up]: "mostly about height, not width" which sounds like resize:grow-vertical. There's also mention of "-moz-available" (need to research that and link it up).
** forward reaching properties/values to enable native-like interfaces
*** 'spell-check'
*** 'grammar-check'
**** both suggested by: [httphttps://lists.w3.org/Archives/Public/www-style/2010Dec/0383.html www-style: Re: Implementing contentEditable in CSS3 UI]*** more "overflow" extensions: httphttps://wiki.csswg.org/spec/css3-overflow
Additional CSS3 UI related features in Mozilla to investigate:
==== CSS3 Element ====
===== element function =====
Firefox 4 implements background: -moz-element(#foo); to use element with id foo as the background per httphttps://hacks.mozilla.org/2010/08/mozelement/
We're pursuing adding element(#foo) as an "at-risk" feature to CSS3.
Proposal (worked with Tab Atkins)
* httphttps://lists.w3.org/Archives/Public/www-style/2010Aug/0635.html* latest: [httphttps://dev.w3.org/csswg/css3-images/#element-reference added to CSS3 Image editor's draft]
Threads:
* [httphttps://lists.w3.org/Archives/Public/www-style/2010Aug/thread.html#msg635 element() 2010-08]* [httphttps://lists.w3.org/Archives/Public/www-style/2010Sep/thread.html#msg0 element() 2010-09]
Thoughts:
* collect new features for CSS3.1/4 Color - color-correction - iterate that on CSSWG wiki:
** search www-style archive for css4-color
** httphttps://wiki.csswg.org/spec/css4-color
* write a first working draft of CSS3.1/4 Color with collected feature(s) (even if it includes just a new color management property)
* find out where Hixie's tests went (was at httphttps://test.csswg.org/source/contributors/hixie/incoming/css3-color/ ) and figure out what to do with them.
=== DOM API vendor prefixing ===
There are three areas of the open web app platform that this has been problematic:
# '''CSS'''. In the past, some properties were implemented, either as spec'd (and the spec was buggy), or in a way that made sense but incompatible with the spec (because the spec didn't make sense or was not useful to web authors), and then we got "stuck" with those implementations and were not able to update/fix the spec and the respective properties and/or values. Examples:
## 'clip' property. mis-specified in CSS 2.0. implemented as presumed intended in IE4/Windows etc. but turned out to be buggy. some content started depending on it. we (CSS WG at the time) were unable to really fix it in a way that implementations could change, though [httphttps://www.w3.org/TR/CSS21/visufx.html#clipping CSS 2.1 tries to fix clip].## 'word-wrap' property. in this case, created/proposed by Microsoft, and [httphttps://web.archive.org/web/20150308232632/https://msdn.microsoft.com/en-us/library/ms531186.aspx msdn.microsoft.com/en-us/library/ms531186.aspx implemented as of IE5.5/Windows ca 2000](Internet Archive link), we are again, kind of stuck with the particular implementation. [https://web.archive.org/web/20160722020847/http://www.codingforums.com/archive/index.php/t-2075.html www.codingforums.com/archive/index.php/t-2075.html] (Internet Archive link) Forum posts as of 2002 were recommending use of the literal word-wrap property]. Though since Microsoft did switch to advocating/supporting a prefixed version '-ms-word-wrap'. Note that it is also [https://developer.mozilla.org/en/CSS/word-wrap supported in Firefox 3.5 ca 2009], and it is in the latest (2007) version of the [httphttps://www.w3.org/TR/2007/WD-css3-text-20070306/#word-wrap CSS3 Text spec which is just a working draft].### See related 'word-break' property ([httphttps://www.w3.org/TR/2007/WD-css3-text-20070306/#word-break word-break in CSS3 Text WD] - latest, 2007), also [https://web.archive.org/web/20131108081707/http://msdn.microsoft.com:80/en-us/library/ms531184.aspx msdn.microsoft.com/en-us/library/ms531184.aspx ] (Internet Archive link) initially (partially) implemented in Internet Explorer 5.x as word-break], and later switched to the prefixed '-ms-word-break'. [https://web.archive.org/web/20131006173053/http://msdn.microsoft.com:80/en-us/library/cc351024(VS.85).aspx msdn.microsoft.com/en-us/library/cc351024%28VS.85%29.aspx ] (Internet Archive link) More on CSS Compatibility and Internet Explorer].
# '''HTML'''. Too many examples to list here. Some browsers are still stuck supporting <code><blink></code> and <code><marquee></code> (which has many odd details), nevermind the classic example of <code><table></code> layout, with tons of odd special cases and error-handling for compat, originally from Netscape's implementation, reverse-engineered by Microsoft in Internet Explorer, which has subsequently been reverse-engineered by every other browser.
# '''DOM'''. In particular [httphttps://www.w3.org/TR/2009/WD-webstorage-20091222/ Web Storage working draft] (e.g. the 'localStorage' attribute/property) was implemented in multiple browsers (IE8+, Chrome, Safari, Opera, Mozilla as of 2010 - date order unknown). By the time people discovered it was not threadsafe as specified, it was too late to change the spec to fix that problem - it would have broken too many apps/sites already written which apparently depended on it.
==== existing solutions ====
===== CSS vendor prefixes case studies =====
* '''border-radius'''. for a few years now browsers have been implementing ''vendor prefixed'' versions of the border-radius properties, web authors have been experimenting on the web, and the spec has iterated/improved based on feedback. Now we have a well-designed and road-tested 'border-radius' property in a CR spec and implementations are implementing that.
* '''word-wrap vs whitespace: pre-wrap'''. interactions between new properties and new values on existing properties. See this [https://web.archive.org/web/20161005144300/http://scottonwriting.net/sowBlog/archive/0000/00/00/163005.aspx scottonwriting.net/sowBlog/archive/0000/00/00/163005.aspx] (Internet Archive link) example of the property vs value interaction] between the new 'word-wrap' property and the (sometimes prefixed) new 'pre-wrap' value on the 'whitespace' property. The point is to show how prefixing can actually work across different approaches to evolving CSS.
===== CSS vendor prefixes successes =====
Several well known web designers and developers have written at length about the successes of CSS vendor prefixes, and how they have both helped avoid problems from before, and actually improve the evolution of CSS.
* [httphttps://www.alistapart.com/articles/prefix-or-posthack/ A List Apart: Prefix or Posthack] by Eric Meyer* [https://web.archive.org/web/20151004052842/http://www.webmonkey.com:80/2010/07/advice-from-the-css-guru-embrace-prefixes/ WIRED Webmonkey: Advice From the CSS Guru: Embrace Prefixes] (original link <nowiki>www.webmonkey.com/2010/07/advice-from-the-css-guru-embrace-prefixes</nowiki> died at some point) by By Michael Calore* [httphttps://www.the-haystack.com/2010/03/22/coping-with-css-prefixes/ The Haystack: Coping with CSS vendor prefixes] by Stephen Hay* [httphttps://snook.ca/archives/html_and_css/not-supported Snook.ca: NOT SUPPORTED] by Jonathan Snook* [httphttps://annevankesteren.nl/2010/03/css-vendor-prefix Anne van Kesteren: In defense of CSS prefixes] by Anne van Kesteren
==== analysis of applicability ====
<pre>vendor_prefix _ unprefixed_name</pre>
E.g. HTML5 has a new [httphttps://www.w3.org/TR/html5/common-input-element-attributes.html#attr-input-pattern 'pattern' attribute], and we've implemented it in Firefox 4. We really should be using:
<pre>moz_pattern</pre>
* CSS3 Flex Box
** current working draft: httphttps://www.w3.org/TR/css3-flexbox/** current editor's draft: httphttps://dev.w3.org/csswg/css3-flexbox/ ** Tab's proposed update: httphttps://dev.w3.org/csswg/css3-flexbox/Overview.new.src.html** Tab's documentation of differences between editor's draft and his draft: httphttps://www.xanthir.com/blog/b48Z0
* CSS3 Grid
** 2007-09-05 (current) working draft: httphttps://www.w3.org/TR/css3-grid/** 2008-01-06 (current) editor's draft: httphttps://dev.w3.org/csswg/css3-grid/
* CSS3 Grid Align - not clear on the relation between Grid and Grid Align
** Alex Mogilevsky's CSS3 Grid Align first draft: [https://web.archive.org/web/20101231085657/http://www.interoperabilitybridges.com/css3-grid-align/www.interoperabilitybridges.com/css3-grid-align] (Internet Archive) link*** Alex's www-style email thread announcing his draft: httphttps://lists.w3.org/Archives/Public/www-style/2010Oct/thread.html#msg787** 2010-11-18 (current) editor's draft: httphttps://dev.w3.org/csswg/css3-grid-align/
Some next-steps:
=== Fullscreen ===
;latest living / development / in progress draft
:httphttps://fullscreen.spec.whatwg.org/
;spec source (for editing)
:https://github.com/whatwg/fullscreen/blob/master/Overview.src.html
;latest snapshot W3C draft
:httphttps://www.w3.org/TR/fullscreen/
;latest snapshot W3C TR-ready draft
:httphttps://dvcs.w3.org/hg/fullscreen/raw-file/tip/TR.html
;W3C branch snapshot spec source
:httphttps://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html
;test suite
:TBD
** https://wiki.mozilla.org/Gecko:FullScreenAPI
* make sure feedback is incorporated and FAQs written from
** httphttps://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/thread.html#27670** httphttps://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-October/thread.html#33503
* iterate based on feedback / implementer experience
=== CSS Waiting For ===
==== CSS3 Backgrounds and Borders ====
Waiting for CR of httphttps://www.w3.org/TR/css3-background/
And then: outstanding UI related issues:
=== Related Features ===
* Context Menu
** see related: 2010-05-03 [httphttps://web.archive.org/web/20101218115210/https://mozillalabs.com/jetpack/2010/05/03/context-menu-module-microformats/mozillalabs.com/jetpack/2010/05/03/context-menu-module-microformats/ ] (Internet Archive link) The Context Menu Module & Microformats] (JetPack)
* ...
social web
* OAuth (including OAuth 2, xAuth)
* [httphttps://activitystrea.ms Activity Streams]* [httphttps://www.w3.org/2005/Incubator/federatedsocialweb/ W3C Federated Social Web Incubator] (formerly: [http://federatedsocialweb.net/ Federated Social Web])
* ...
communities
* WhatWG
** [httphttps://wiki.whatwg.org/wiki/index.php?title=Special:RecentChanges &days=183&from= WHATWG wiki changes] - delete/block spam
== Events ==
* W3C Process. Work on improving W3C processes:
** httphttps://wiki.csswg.org/spec/process (proposal for improving CSSWG processes)
** 2012-02-16 [https://www.w3.org/2012/02/16-ab-whiteboard W3C AB Whiteboard on Agility Issues] (Member only link, notes of my meeting with the W3C AC on improving proces)
==== Annual Summaries ====
===== 2011-06-15 - 2012-06-15 =====
* 2011-11 W3C TPAC BarCamp - ran first ever W3C TPAC BarCamp day - to great reviews (best TPAC plenary day ever).
* 2011-11 [[HTML5]] <time> - restored the <time> element in HTML5, enhanced it to fit author needs.
* CSS Styling Attribute - achieved CR!
;latest published draft (CR)
:httphttps://www.w3.org/TR/css-style-attr/
;latest development / in progress draft
:httphttps://dev.w3.org/csswg/css-style-attr/
;spec source (for editing)
:httphttps://dev.w3.org/csswg/css-style-attr/Overview.src.html
;test suite
:TBD
:TBD
;issues list for the current draft
:httphttps://wiki.csswg.org/spec/css-style-attr
* Hixie update reference to CSS Style Attribute draft in [httphttps://www.whatwg.org/specs/web-apps/current-work/multipage/references.html#references HTML5 References]
** emailed 2011-080
** fixed 2011-165
* CSS3 Color draft - achieved PR!
;latest published draft
:httphttps://www.w3.org/TR/css3-color/
;latest development / in progress draft
:httphttps://dev.w3.org/csswg/css3-color/
;spec source (for editing)
:httphttps://dev.w3.org/csswg/css3-color/Overview.src.html
;test suite
:httphttps://www.w3.org/Style/CSS/Test/CSS3/Color/20080721/
;implementation reports of the test suite
:httphttps://www.w3.org/Style/CSS/Test/CSS3/Color/current/reports/
;issues list for the current last call
:httphttps://wiki.csswg.org/spec/css3-color
===== CSS3 UI =====
Updated [httphttps://dev.w3.org/csswg/css3-ui/ CSS3 UI Editor's draft] with:
====== pointer-events ======
* add '''pointer-events''' A way of specifying whether an element is opaque to pointer events (and receives them) or is transparent to them (letting them get handled by what's underneath.
** CSSWG wiki: httphttps://wiki.csswg.org/ideas/pointer-events
** https://developer.mozilla.org/en/css/pointer-events - Mozilla spec
*** shipped in Firefox 3.6 - demo: [https://web.archive.org/web/20120410031737/http://demos.hacks.mozilla.org/openweb/pointer-eventsdemos.hacks.mozilla.org/ openweb/pointer-events] (Internet Archive link) [https://bugzilla.mozilla.org/show_bug.cgi?id=380573 bug 380573]).
*** See also SVG version: https://wiki.mozilla.org/SVG:Pointer-events
** httphttps://webkit.org/specs/PointerEventsProperty.html - Webkit spec
*** shipped in Safari 4.0 ([https://bugs.webkit.org/show_bug.cgi?id=11395 bug 11395])
** [https://web.archive.org/web/20130830194359/http://people.opera.com/lstorset/TR/pointer-events/ people.opera.com/lstorset/TR/pointer-events] (Internet Archive link) Opera proposal]*** [httphttps://lists.w3.org/Archives/Public/www-style/2010Aug/0407.html email proposing]*** [https://web.archive.org/web/20130830194402/http://people.opera.com/lstorset/TR/pointer-events/ED-pointer-events-20100820.html people.opera.com/lstorset/TR/pointer-events/ED-pointer-events-20100820.html] (Internet Archive link) CSS Hit Testing]
** related: [[SVG:Pointer-events]]
** key issue: precisely define default behavior (auto or visible etc.)
* '''text-overflow'''. incorporated '[https://developer.mozilla.org/En/CSS/text-overflow text-overflow]', since it's more a UI/overflow thing than a typesetting thing. There are at least 3 implementations (IE, WebKit, Opera), and has a bug against Firefox: [https://bugzilla.mozilla.org/show_bug.cgi?id=312156 312156]
** Wanted for post-FF4; mats will be working on it, needs spec
** W3C: httphttps://dev.w3.org/csswg/css3-text/#text-overflow*** httphttps://www.w3.org/blog/CSS/2009/11/25/resolutions_84 for bidi discussions
** DevMo: https://developer.mozilla.org/En/CSS/text-overflow
** Webkit: httphttps://developer.apple.com/library/safariarchive/documentation/appleapplicationsAppleApplications/referenceReference/SafariCSSRef/Articles/StandardCSSProperties.html#//apple_ref/doc/uid/TP30001266-SW24** Microsoft/IE: [https://web.archive.org/web/20130112221116/http://msdn.microsoft.com/en-us/library/ms531174(VS.85).aspxmsdn.microsoft.com/en-us/library/ms531174(VS.85).aspx] (Internet Archive link)
** write test cases for 'ellipsis' and 'clip' (default value) and confirm cross-browser support.
** Details that [https://bugzilla.mozilla.org/show_bug.cgi?id=312156#c21 RoC wants]:
*** If an ellipsis, where does the ellipsis go?
**** it goes instead of the image and any text you have to remove in order to make the ellipsis fit.
** add httphttps://farm4.static.flickr.com/3635/3571013052_d419aff822_s.jpg CSS IS AWESOME examples/tests to the spec
** capture issues and undefined aspects from fantasai/RoC emails as of 2011-031.
** clarify text per emails from fantasai/RoC
*** the effect of text-overflow:ellipsis on lines whose line boxes are not direct children of the block box(es) with text-overflow.
*** the behavior of text-overflow:ellipsis on a block with 'overflow' of 'scroll' (no good interop, ideal behavior documented, needs screenshots)
**** testcase from RoC: httphttps://lists.w3.org/Archives/Public/www-style/2011Jan/att-0669/test.html
**** Safari scrolls the ellipsis ... and doesn't reveal any additional text - this doesn't make sense to me (RoC, nor me Tantek) as a user. If I scroll I should get to see the rest of the content. (Agreed)
**** Opera scrolls the text into view until the you can see the end of the text at which point the block scrolls no further (this is ideal beahvior -t). No ellipsis is display on the otherside of the block when you start scrolling characters off the start edge.
For more details on completed events, see the main [[Events]] page and its archives.
===== Events 2010 =====
* June 1-3 Open Source Bridge, Portland, OR, http://opensourcebridge.org* June 28-30 Voices That Matter Web Design in SF [https://web.archive.org/web/20101012000437/http://www.voicesthatmatter.com/webdesign2010/ www.voicesthatmatter.com/webdesign2010] (Internet Archive link)** [https://www.flickr.com/photos/bgavin/sets/72157624312745705/ Flickr photoset]: [https://www.flickr.com/photos/bgavin/4768326845/in/album-72157624312745705/ 1], [https://www.flickr.com/photos/bgavin/4768329629/in/album-72157624312745705/ 2], [https://www.flickr.com/photos/bgavin/4768983440/in/album-72157624312745705/ 3]
* July 6-10 [[Summit2010|Mozilla Summit]] in Whistler, Canada.
* July 13 [https://web.archive.org/web/20100815062956/http://www.realestateconnect.com/program/ www.realestateconnect.com/program/] (later moved to [https://web.archive.org/web/20101025001531/http://www.realestateconnect.com/sf10/program/ www.realestateconnect.com/sf10/program/ ], both Internet Archive links). Real Estate Connect San Francisco] . (Original version required a click on "Workshops »", search for "HTML5") at Hilton San Francisco Union Square, 333 O'Farrell Street, San Francisco, California
** participating in WORKSHOP: ConnectTech / HTML5 Is Coming, Are You Ready?
* July 17 [https://web.archive.org/web/20100705145947/http://openwebcamp.org :80/ openwebcamp.org] (Internet Archive link) OpenWebCamp II] at Stanford* July 18 [https://web.archive.org/web/20100721235242/http://federatedsocialweb.net:80/wiki/Main_Page federatedsocialweb.net/wiki/Main_Page] (Internet Archive link) Federated social web summit] ([https://web.archive.org/web/20100726175723/http://federatedsocialweb.net/wiki/Schedule federatedsocialweb.net/wiki/Schedule] — Internet Archive link for the schedule])** more info: [https://web.archive.org/web/20100814132804/http://status.net/2010/06/28/federated-social-web-summit-2010-announced status.net/2010/06/28/federated-social-web-summit-2010-announced] (Internet Archive link) announcement], [https://web.archive.org/web/20100809183536/http://federatedsocialweb.net/wiki/FedAll2010/Invitations federatedsocialweb.net/wiki/FedAll2010/Invitations] (Internet Archive link for attendees])* August 23-25 [httphttps://www.w3.org/Style/Group/2010/Oslo W3C CSS WG f2f in Oslo]* September 1-3 [httphttps://2010.dConstruct.org/ dConstruct in Brighton] - web design and development* September 9 [https://web.archive.org/web/20110824235723/http://plancast.com/p/27av plancast.com/p/27av] (Internet Archive link) MozPub HTML5 meet, with Tantek Çelik] - gather input for HTML5 improvements* September 21-25 [https://web.archive.org/web/20101118070934/http://usa10.webdirections.org:80/ usa10.webdirections.org] (Internet Archive link) Web Directions USA] - represent Mozilla in Browsers panel, gather input for HTML5, CSS3.Atlanta, GA
* 2010-10-01...2010-10-02 Open Video Conference, gather input for HTML5 video/media etc.
* 2010-10-03 OVC hack labs - gather input for HTML5 video/media etc.
* 2011-04-19...2011-04-21 Where 2.0 - gather input on GeoLocation additions, browser support for geo apps
* 2011-04-22 WhereCampSF SF 2011 - gather input on browser support for geo apps
* ...
* 2011-07-16 [https://web.archive.org/web/20110922113459/http://www.openwebcamp.org/ Open Web Camp III] (Internet Archive link) - at Stanford, California, United States.
** speaker - on CASSIS. See also [https://web.archive.org/web/20110904001618/http://openwebcamp.org/attendees attendees] (Internet Archive link)
For more, see: [[Events/2011]]
===== Events 2012 =====
See: [[Events/2012]]
* July 14 [https://web.archive.org/web/20130425064142/http://openwebcamp.org/ openwebcamp.org] (Internet Archive link) OpenWebCamp IV at San Jose, California
** [https://web.archive.org/web/20130516145144/http://openwebcamp.org/events/56 HTML5 and microformats 2 - the next evolutionary step for web data]
===== Events 2013 =====
See: [[Events/2013]]
===== Events 2014 =====
See: [[Events/2014]]
