-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/28/2014 01:42 AM, Domenic Denicola wrote:
TL;DR: we (Google) are trying to explain the platform with custom
elements
[citation needed] on explain the platform.
- --
Ms2ger
-BEGIN PGP SIGNATURE-
Hi Steve, thanks greatly for your help. It's clear now that I should have
reached out to you for your expertise directly before being very wrong on a
public mailing list :)
From: Steve Faulkner faulkner.st...@gmail.com
It appears (please correct me) you have made the assumption that 'strong
From: Nick Krempel ndkrem...@google.com
Have you considered allowing ARIA attributes to be set on a shadow root.
The semantics would be that the browser uses the value of an ARIA attribute
on the (most recent) shadow root for an element, and only if it's not set
there will it fall back to
On Wed, 27 Aug 2014, Daniel Appelquist wrote:
As you might know, the new charter for webapps includes a new version
of the URL spec. I am acting as editor of this spec.
What's the purpose of the W3C republishing this spec?
--
Ian Hickson U+1047E
On Thu, Aug 28, 2014 at 10:04 AM, Ian Hickson i...@hixie.ch wrote:
On Wed, 27 Aug 2014, Daniel Appelquist wrote:
As you might know, the new charter for webapps includes a new version
of the URL spec. I am acting as editor of this spec.
What's the purpose of the W3C republishing this
WebApps received a Request for Comments re DAPWG's August 28 Last Call
WD of Battery Status API (last published as a [CR], see [Diff]):
http://www.w3.org/TR/2014/WD-battery-status-20140828/
Individual WG members are encouraged to provide individual feedback.
If anyone in WebApps wants
Thanks to all for their responses. The fact that I misread a bunch of authoring
requirements as UA requirements made things a lot more complicated than they
are in reality.
I updated my ARIA summary [1] and illustrative scenarios [2] to reflect the
actual spec/browser behavior. And, given the
On Thu, 28 Aug 2014, Glenn Adams wrote:
On Thu, Aug 28, 2014 at 10:04 AM, Ian Hickson i...@hixie.ch wrote:
On Wed, 27 Aug 2014, Daniel Appelquist wrote:
As you might know, the new charter for webapps includes a new
version of the URL spec. I am acting as editor of this spec.
Why not put the `implicitAria` role on the element's prototype?
That way each instance can override with the attribute in a naive and
natural manner: `el.role = link`.
This would necessitate some getter/setter logic for the aria properties to
handle the something like the details case with
