Re: [w3c/webcomponents] Focus delegation from shadow host should not behave like sequential focus navigation (#830) from Ryosuke Niwa on 2019-09-09 (public-webapps-github@w3.org from September 2019)

From: Ryosuke Niwa <notifications@github.com>
Date: Mon, 09 Sep 2019 14:11:24 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/830/529668670@github.com>

> I agree, which is why I was a bit surprised by folks pushing to standardize a specific order. Given that different browsers explicitly want to have different choices for what elements are click-focusable, I don't see any way of avoiding the result being UA-dependent. So shall we just go with that?

Well, there is a subtle difference between allowing UA to skip any element and skip only ones that are not mouse focusable. If we defined the order and defined so that UA can only skip non-mouse focusable element, then the first element is more or less fixed. e.g. UA can't use tab index order as opposed to flat tree order since the first mouse focusable element wouldn't be the first element in the tab index order.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/830#issuecomment-529668670

Received on Monday, 9 September 2019 21:11:47 UTC