Jihye Hong

Hi @EloB, I think this polyfill won't work with canvas/webGL. In general, the polyfill moves the focus among focusable DOM elements. Therefore the canvas element will be considered as just...

The test cases in the web platform test format have been added in - https://github.com/WICG/spatial-navigation/tree/master/tests , both for spec and UX point of view. Specifically for the expected result of...

@joe-watkins, thanks for raising this issue. I think your opinion is reasonable when thinking of an accessibility point of view. Other than people who may have mobility/dexterity disabilities, sometimes people...

@jayarjo Thanks for your feedback! Yes, as you pointed out, there wasn't the procedure about preventing the navigation events in the previous polyfill. I updated the polyfill with https://github.com/WICG/spatial-navigation/pull/156, and...

@jayarjo Yes, the flags are used for defining the prevent default behavior for the navigation events. Those flags are set as `true` when the events are triggered. And if those...

@domenic Thank you for your significant input and for sharing the related issue. I'm sorry for the late reply. I need to think more about how to handle the language...

I'm sorry for the confusion, but for now, we've decided that the language detection feature is not considered in the local dictionary API. So, I would like to change what...

I'm closing this issue since the spec is updated * https://drafts.csswg.org/css-pseudo-4/#selectordef-search-text by https://github.com/w3c/csswg-drafts/pull/10475

I've also investigated this issue, and here is my opinion: > 1. **Should `getComputedStyle(x, "::search-text")` return the `:current` styles or the `:not(:current)` styles?** We propose `:not(:current)`, and specifying this behaviour...

@fantasai , In[ the resolution ](https://github.com/w3c/csswg-drafts/issues/10212#issuecomment-2089302563), this feature needs to be marked as optional to implement. How can I put it in the spec?