- From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
- Date: Thu, 07 Nov 2013 09:31:58 +0100
- To: www-style@w3.org
On 07/11/13 08:37, Simon Pieters wrote:
> No, we should add things based on use cases.
Simon, this is not the WHATWG here. We add things based on consensus,
whatever the consensus means. Based on use cases only, we would
be VERY far away from the feature level of the Web today...
> $('img[alt]').attr('alt')
jQuery or toolkits are not a long-term workable solution and I find
hilarious to see jQuery mentioned here while all browser vendors
introduce themselves tons of proprietary selectors to do the things
they don't want to do in jQuery. Sometimes selectors that were rejected
by the WG.
Simon Sapin said:
> We should not add features "for the sake of completeness" if there is no use case.
Right, but completeness does matter and that's why W3C has the TAG.
> (I’m not saying there is no use case, but I haven’t seen them yet for selecting text, comment and processing instruction nodes.)
For I18N a comment is valuable information that may need to be
translated. ITS then needs to select such nodes. PIs, CDATA sections
often are used in the non-html world of technical documentation that
also needs ITS.
</Daniel>
Received on Thursday, 7 November 2013 08:32:20 UTC