Section | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Code Block |
---|
<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1"> </head> <body> <div><p>Here is a div with some text. How long is this text? It should wrap around to the next line since it is a long enough line</p></div> <script xmlns="http://www.w3.org/1999/xhtml" src="http://<server>:<port>/frevvo/web/tn/frevvo.com/u/8aa27da6-4bef-427c-92e3-6ad8d58e506a/app/_bDd4YX76EduXFsA4l9RQeQ/formtype/_RwO0sMxjEeKp6swhthjzZQ/embed?container=false&center=false&resize=true&border=false" type="text/javascript"> </script> </body> </html> |
Unsaved Changes Warning Message
Data loss is possible if users filling in a lot of data in a long forms/flows close the browser ot tab without saving or submitting. Users are now warned of this situation before the data loss. This applies to use-mode forms and flows only, not edit mode. The warning only shows if there have been changes made to the form/flow. If there are no changes, then no warning is displayed. If the form/flow is Saved or the Save on Navigate feature is configured for a flow, then changes are saved and the warning is not produced on any attempt to close the browser.
The unsaved changes warning feature is not supported on iOS Safari and only partially supported on Chrome Android. You may notice some inconsistencies with workflows. Refer to the Unsaved Changes topic for the details.
The warning behavior message is browser specific. The messages for Firefox, Chrome and Microsoft Edge are shown below:
Column | ||
---|---|---|
| ||
Firefox browser |
Column | ||
---|---|---|
| ||
Google browser |
Column | ||
---|---|---|
| ||
Microsoft Edge browser |
Unsaved Data Message and Workflows
Certain browsers (chrome and firefox, but not IE11 and Edge) will not show the Unsaved Data message on closing the browser window/tab if the user does not click on something.
The Unsaved Changes feature may not work reliably with flows in the following scenarios:
- A user makes a change on step 1 of a screenflow, selects continue but makes no change at all on step 2. They then immediately close the window. No prompt is displayed.
- A screenflow has a Summary step. There are unsaved changes and when the user gets to the Summary step they close the window. No prompt is displayed.