Probably doesn't matter which group does it since it'd end up being me
doing the work either way... At the time where I made that comment, the
CSSWG was planning on creating a CSSOM spec to replace the DOM2 CSS spec.
That plan still vaguely exists, though it isn't a high priority for the
CSS group.
I can certainly see myself speccing a getElementsBySelector() API as part
of Selectors 2. But either way, the spec for gEBS is simple; it returns
the same type as getElementsByTagName(), it is accessible from Document
and Element nodes and selects a subset of the descendants of that node, it
takes a single argument (a string representing a selector), its first
version doesn't support namespaces, and it raises an exception SYNTAX_ERR
if the string can't be successfully parsed by the UA.
[10]
ACTION-87: Selectors API from Anne van Kesteren on 2006-02-25 (public-webapi@w3.org from February 2006) http://lists.w3.org/Archives/Public/public-webapi/2006Feb/0108.html
(名無しさん2006-02-26 02:46:14 +00:00)
During the F2F I got an action assigned to me to draft something up for
getElementsBySelector().
[17] 以後の動きについては選択子APIの項を参照。
CSSValue
[11]
Re: [SVGMobile12] SVGT12-207: Conformance to uDOM from Ian Hickson on 2006-01-03 (www-svg@w3.org from January 2006) http://lists.w3.org/Archives/Public/www-svg/2006Jan/0066.html
(名無しさん2006-02-16 03:07:36 +00:00)
There are plans for making big improvements to the CSSOM ...
[2]
[CSSOM] CSSValue and related interfaces (message from the CSS WG) from Bert Bos on 2003-10-30 (www-style@w3.org from October 2003) http://lists.w3.org/Archives/Public/www-style/2003Oct/0347
One of the specifications that the CSS WG is chartered to write is a new
version of the Document Object Model for CSS, or CSSOM for short. We don't
have a Working Draft yet, but the following is is an official statement by
the CSS. It represents the current consensus in the WG:
The following DOM2 Style features are considered to be problematic
and are therefore classified as obsolete. Implementors are strongly
urged not to implement them. Replacements will be provided at some
future point.
The UnknownRule interface (unknown rules should be dropped by
the parser and thus never reach the DOM)
The getPropertyCSSValue method, CSSValue interface, all
interfaces inheriting from CSSValue, and the RGBColor, Rect, and
Counter interfaces (the CSSValue interface is thought to be too
awkward for frequent use)
[37] [CSSOM] CSSValue and related interfaces (message from the CSS WG)
( (Bert Bos 著, 版))
http://lists.w3.org/Archives/Public/www-style/2003Oct/0347.html
[48] CSS Object Model (CSSOM)
( ( 版))
http://www.w3.org/TR/2013/WD-cssom-20131205/
[49] Web Applications 1.0 r8390 Update how the interaction with CSS style sheets and CSSOM is defined.
( ( 版))
http://html5.org/tools/web-apps-tracker?from=8389&to=8390
[67][css-animations][css-conditional][css-font-loading][cssom-view][cssom][mediaqueries] IDL: Use [Exposed] consistently by zcorpan · Pull Request #1749 · w3c/csswg-drafts
()
https://github.com/w3c/csswg-drafts/pull/1749
[68] Add me as an editor of CSSOM as resolved in the Berlin F2F.
(emilio著, )
https://github.com/w3c/csswg-drafts/commit/35f433a226871a26287f9d9e1470345068eb132f