Using `registry.js` here was causing **two copies** of `registry` to be included — the copy from files that `require('registry')` and the copy from files that `require('registry.js')`. As a result, certain global variables/properties in `registry` were not initialized in one copy, but were in the other. To work around this issue, this pull request changes all `registry.js` imports to `registry` imports. Perhaps using [`metro` instead of `webpack`](https://github.com/necolas/react-native-web/issues/1257) would be a different way to address this issue?

I'm not sure that this is true...

**Related regression testing**: - On Android 13, I have verified that: 1. The "select date time" dialog can be opened from the note actions menu for a to-do (from "set alarm"). 2. Clicking "set date" shows a date/time selection dialog. 3. Clicking "save alarm" asks for alarm permissions (I hadn't previously granted them to Joplin). 4. Clicking "clear alarm" clears the alarm.

Works around an issue where log lines weren't showing on web.

`flex` styling is handled slightly differently in `react-native-web` when compared to `react-native`. In particular, [`flex-basis`](https://developer.mozilla.org/en-US/docs/Web/CSS/flex-basis) (the default `flex` size) seems to default to `0` in some cases.

`showDirectoryPicker` is currently unsupported in most browsers that aren't Google Chrome. Currently, the file input is disabled in this case (see the `if (!supported` change below).

To prevent the markdown toolbar from being invisible on web, different logic for hiding/showing the markdown toolbar's overflow menu was needed.

Currently, `Alert.alert` doesn't work with `react-native-web`. This file provides an API compatible with `Alert` that does work on web.

It might be better to use the inline edit icon on all platforms (at present, it's a hardcoded placeholder and is slightly different from the Ionicon `pencil` icon). 

This is a hack to allow KaTeX and other CSS files to load fonts and other similar resources with `url(...)` syntax. Like note resources, plugin assets are stored in [a virtual filesystem](https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Origin_private_file_system). As such, `src: url(./some-resource.ttf)` won't work. This function replaces `url(./some-resource.ttf)` syntax with `url(...some working URL here...)`, allowing these resources to load.

On web, resources are stored in a **virtual** file system ([OPFS](https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Origin_private_file_system)). As such, to show them with `<img>`/`<video>` and tags, we need to create URLs for them.

Currently, this is used by the markdown toolbar.

Related documentation: - https://developer.mozilla.org/en-US/docs/Web/API/HTMLIFrameElement/allow - https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/sandbox

`aria-hidden={true}` is the web version of the "hide from screen readers and other accessibility tools". Currently, we use `accessibilityElementsHidden={true}` for this on iOS and `importantForAccessibility='no-hide-descendants'` on Android. Also see the new `components/accessibility/AccessibleView.tsx` file.

`DialogManager.tsx` was added due to the lack of support for `Alert.alert` in `react-native-web`. On web, it manages showing custom dialogs based on `react-native-paper`, with an `Alert.alert` compatible API. On other platforms, it continues to show dialogs with `Alert.alert`. It also sets `shim.showMessageBox`, allowing plugins and other related code to use the custom dialogs. Screenshot: 

Currently, this is disabled by default because no user-visible reason is shown for why location permission is requested. The "Allow location access" prompt is shown when first creating a new note (after enabling location tracking), but there isn't any context for why Joplin wants to track the user's location. Currently, however, I don't think the existing mobile app explains why location permissions are being requested. As such, for consistency, it could make sense to remove this different default: ```suggestion ```

We might be able to use the [Web Notification API](https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API) for this. However, the app might need to be open for this to work (alternatively, we could use the [background sync API](https://developer.mozilla.org/en-US/docs/Web/API/Background_Synchronization_API), but this might not be accurate enough for alarm scheduling).