From df0d0d487ed4b38cdb531dfdd97d56e74774644c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Emilio=20Cobos=20=C3=81lvarez?= <emilio@crisal.io>
Date: Thu, 9 Jul 2020 03:33:26 +0200
Subject: [PATCH] Add position for the inert attribute. (#371)

Mark it as worth-prototyping as per this comment[1] and following.

Closes #4288, let's continue the more technical discussion somewhere
else, like in https://github.com/whatwg/html/issues/5650.

[1]: https://github.com/mozilla/standards-positions/issues/174#issuecomment-590227139
---
 activities.json | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/activities.json b/activities.json
index 7cdd72ae..058597a0 100644
--- a/activities.json
+++ b/activities.json
@@ -1178,6 +1178,18 @@
     "title": "enterkeyhint attribute",
     "url": "https://html.spec.whatwg.org/multipage/interaction.html#attr-enterkeyhint"
   },
+  {
+    "ciuName": "mdn-api_htmlelement_inert",
+    "description": "Allow arbitrary DOM subtrees to become inert",
+    "id": "inert-attr",
+    "mozBugUrl": "https://bugzilla.mozilla.org/show_bug.cgi?id=921504",
+    "mozPosition": "worth prototyping",
+    "mozPositionDetail": "A high-level tool for authors to achieve some of these use cases while getting a11y right seems useful",
+    "mozPositionIssue": 174,
+    "org": "WHATWG",
+    "title": "inert attribute",
+    "url": "https://github.com/whatwg/html/pull/4288"
+  },
   {
     "ciuName": null,
     "description": "Proposal to add various output attributes on HTML's &lt;input> elements that would allow developers to declare some conversions the browser could do to, for example, images and videos.",