1. Interception enabled by the event subscription to the input.fileDialogIntercepted event.
2. Dialog is suppressed, not shown on screen, does not block, the input.fileDialogIntercepted event is emitted referencing the file input element.
3. If the client chooses to fill out the element, they use input.setFiles. The cancellation event is not testable (does not seem important).
4. Calling input.setFiles is possible without intercepting the dialog. Calling it does not trigger the dialog.
5. Without the interception, the dialog is still shown. Or handled as the result of another issue for addressing the unhandled events