T299267 implements a "hint" that enables people to switch between the New Discussion Tool and the existing `section=new` experience.
This task involves the work with clarifying how – if at all – drafted text in either experience will be saved when switching back and forth between the two.
=== Behavior
1. Open the New Discussion Tool for the first time on a wiki where it's just been made available by default
2. Type some text into the `Title` or `Description` field
3. Click the `switch back to the legacy experience` link that appears in the "hint" above the `Title` text field
4. Notice the browser presents a dialog that asks: `Leave site? Changes you made may not be saved.`
5. Click {nav Leave}
6. Arrive in the legacy `section=new` experience
7. Type some text into the `Subject:` or description fields
8. Click the `return to the new experience` link that appears in the "hint" above the `Subject:` text field
**Actual**
9. ❗️ Arrive back in the New Discussion Tool and notice the text you typed in "Step 2." reappears
10. Click the `switch back to the legacy experience` link that appears in the "hint" above the `Title` text field because you realize that you actually do want to use that experience instead of the New Discussion Tool
11. ❗️Notice the form appears empty. Said another way: the text you entered in "Step 7." does NOT appear
!!...it is the inconsistency in "Step 9." and "Step 11.", and the confusion/unmet expectations we anticipate it will cause people, that's leading us to document this issue.!!
**Desired**
9. ✅ Arrive back in the New Discussion Tool and notice the text you typed in "Step 2." does NOT appear
10. Click the `switch back to the legacy experience` link that appears in the "hint" above the `Title` text field because you realize that you actually do want to use that experience instead of the New Discussion Tool
11. ✅Notice the form appears empty. Said another way: the text you entered in "Step 7." does NOT appear
=== Approaches
//Below are the approaches we considered for setting a clear expectation that the changes people make within the New Discussion Tool or legacy `section=new` experience will NOT be saved when switching back and forth between the two.//
**Approach #1: OOUI Dialog**
- Show the `Are you sure?` OOUI dialog [i] AND explicitly discard the changes people will have made in "Step 2." and/or "Step 7."
**Approach #2: *Modified* OOUI Dialog**
- Show a = version of the `Are you sure?` OOUI dialog adapted to this context AND explicitly discard the changes people will have made in "Step 2." and/or "Step 7."
-- //By "adapted" I mean changing the copy that appears within the dialog so people know they are discarding the topic they've written *in order to* switch to the legacy experience. The existing dialog's copy makes no reference to switching interfaces.//
**Approach #3. Browser Dialog**
- Continue showing the browser's `Are you sure?` dialog AND explicitly discard the changes people will have made in "Step 2." and/or "Step 7."
//Note: that in implementing one of the approaches above we are creating the potential for people to wonder why the New Discussion Tool saved changes they've made when navigating away from the New Discussion Tool in subsequent uses despite it not doing so the first time they used it. We are okay with this potential because we think: 1) most people would be pleased to learn the tool recovered changes they thought were lost and 2) in this "first use" case, the tool will have informed people the changes they made will NOT be saved.//
=== Done
- [ ] "Desired" behavior is implemented
---
i. {F34918766}
ii. {F34918769}