We chatted a little bit on matrix and I'm not sure if your comment was before or after so I might be repeating some points I made in chat. I think we don't need `TRY_APP_LINK`, the fact that we have an app registered for a given link can be a property of the matcher and then apps can decide whether to `PROMPT` for those. I also starting to think that having `DENY` doesn't make a lot of sense. The majority of the `DENY` use cases are for the app to do something else instead, so really the only options that we need are `ALLOW` (if the app doesn't have to do anything about this load) or `PROMPT` if the app needs to deny the load and do something else instead (or if it needs more information to check if the load should go through) would that be enough to express our use cases? I would really hope we can avoid implementing a full fledged boolean logic.
Bug 1734923 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We chatted a little bit on matrix and I'm not sure if your comment was before or after so I might be repeating some points I made in chat. I think we don't need `TRY_APP_LINK`, the fact that we have an app registered for a given link can be a property of the matcher and then apps can decide whether to `PROMPT` for those. I also starting to think that having `DENY` doesn't make a lot of sense. The majority of the `DENY` use cases are for the app to do something else instead, so really the only options that we need are `ALLOW` (if the app doesn't have to do anything about this load) or `PROMPT` if the app needs to deny the load and do something else instead (or if it needs more information to check if the load should go through) would that be enough to express our use cases? I would really hope we can avoid implementing a fully fledged boolean logic.