You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.
I'm noticing <template> used a lot for the modals. Seems ones like the device-manager-modal-tpl could be implemented with the <dialog> element and things could be cleaner in terms of setup.
Any specific reason template was used?
This is entirely low-priority if it is decided to change. Not a big deal since we need to focus on function over form atm.
The text was updated successfully, but these errors were encountered:
having unnecesary nodes in the DOM (like hidden modals).
Since <template> helps to avoid these two, and is natively supported, I thought I'll give it a try. Haven't really considered <dialog> though. If it really simplifies the code and doesn't contradict any of the two assumptions that I've made at the top, then we should implement it.
I'm not sure how dialog interacts at the DOM level compared to template. I will do some research on that as time permits. It is however native in Chrome (no other browsers, but this isn't an issue here.) It probably wouldn't simplify the execution code too much, but would remove whatever is currently making the modals as a dependency. We'd just need to manually style the dialog which isn't a major issue.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm noticing
<template>
used a lot for the modals. Seems ones like thedevice-manager-modal-tpl
could be implemented with the<dialog>
element and things could be cleaner in terms of setup.Any specific reason template was used?
This is entirely low-priority if it is decided to change. Not a big deal since we need to focus on function over form atm.
The text was updated successfully, but these errors were encountered: