-
Updated
Sep 26, 2021 - JavaScript
immutablejs
Here are 332 public repositories matching this topic...
-
Updated
Mar 7, 2019 - JavaScript
-
Updated
Mar 3, 2021 - JavaScript
-
Updated
Apr 28, 2022 - JavaScript
-
Updated
Apr 12, 2017 - JavaScript
-
Updated
Apr 12, 2022 - JavaScript
-
Updated
Jan 5, 2021 - TypeScript
-
Updated
Apr 9, 2022 - JavaScript
-
Updated
Aug 12, 2021 - JavaScript
-
Updated
Sep 5, 2018 - JavaScript
-
Updated
Apr 9, 2022 - TypeScript
-
Updated
Feb 10, 2022 - TypeScript
-
Updated
Mar 14, 2021 - JavaScript
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Oct 28, 2019 - JavaScript
-
Updated
Jun 22, 2022 - JavaScript
-
Updated
Jun 22, 2022 - JavaScript
-
Updated
Mar 30, 2017 - JavaScript
-
Updated
Jul 8, 2018 - JavaScript
-
Updated
May 26, 2022 - JavaScript
-
Updated
Jun 30, 2022 - TypeScript
-
Updated
Apr 28, 2022 - JavaScript
-
Updated
Sep 17, 2018 - JavaScript
-
Updated
Aug 29, 2017 - JavaScript
-
Updated
Aug 18, 2020 - JavaScript
-
Updated
Jan 11, 2017 - JavaScript
-
Updated
Sep 7, 2020 - JavaScript
Improve this page
Add a description, image, and links to the immutablejs topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the immutablejs topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Description
Given there's a content collection on the page that does not allow any content to be inserted, it is still possible to invoke the node creation dialog. This is a minor issue, since it doesn't make much sense to have such a content collection in the first place, but nevertheless, the "Add Node" button should be disabled in this scenario.
This behavior is possibly related to #