Hi,
I've started keeping track of all the feature requests for Selectors
API 2 in Bugzilla.
http://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWGcomponent=Selectors+API
I'll start investigating these features after I get the major issues in
the current spec sorted out. If anyone
Hi Cynthia,
On Fri, Jul 11, 2008 at 9:50 PM, Cynthia Shelly
[EMAIL PROTECTED] wrote:
Hi,
I'm a member of wai-pf and wcag, and met some of you at the web apps face to
face in redmond recently. I was reading through the widgets 1.0 requirements
spec, and came across this accessibility
On Jul 14, 2008, at 8:15 AM, Lachlan Hunt wrote:
Boris Zbarsky wrote:
On Mon, 14 Jul 2008 03:40:44 +0200, Lachlan Hunt [EMAIL PROTECTED]
wrote:
Would it be acceptable if I defined one, but made it optional for
implementers to support? Or at least optional for ECMAScript
On Mon, 14 Jul 2008 20:26:23 +0200, Maciej Stachowiak [EMAIL PROTECTED]
wrote:
Since implementing the feature string is trivial, I'd rather it be
mandatory. I agree that feature strings are not a great mechanism, but
optional features are a greater harm than feature strings.
When I
Maciej Stachowiak wrote:
On Jul 14, 2008, at 8:15 AM, Lachlan Hunt wrote:
To avoid forcing implementers to bother implementing such a useless
feature, and potentially lying about their support. Basically, this
should only be for languages other than ECMAScript that don't have
other
On Mon, 14 Jul 2008 21:30:18 +0200, Boris Zbarsky [EMAIL PROTECTED] wrote:
Anne van Kesteren wrote:
How do I select all the inline SVG images on the page?
div svg, p svg
though it's not quite as thorough as your solution.
Offhand, you're missing td, span, body to cover any sort of
