[MGNLUI-6360] Deleted nodes stay in value context in JCR Browser Created: 26/Oct/20  Updated: 16/Sep/21  Resolved: 16/Sep/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Adam Siska Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLUI-6838 JCR browser keeps mgnl:tmpDeleted$Nod... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Migrate JCR Browser

 Description   

Deleted node stays selected in JCR Browser so e.g. this is possible:

Reproduction steps:
0) open JCR Browser
1) create TEST node
2) delete TEST node

Expected:

  • no item should be selected, i.e. root actions should be available

Actual result:

  • deleted node is still selected and one can
    3) click 'Add property'

which brings the TEST node back


Generated at Mon Feb 12 09:35:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.