From: Dominik Csapak <d.csapak@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [yew-devel] [PATCH yew-widget-toolkit] dialog: put all dialogs into a portal
Date: Fri, 2 May 2025 15:04:08 +0200 [thread overview]
Message-ID: <20250502130408.3893193-1-d.csapak@proxmox.com> (raw)
otherwise, the dialog is part of the markup where we insert it, which
can make problems with event handling, for example:
Creating a form that can open a dialog which contains also a form,
produces two problems:
* nesting forms is explicitly not allowed [0]
* if the form has a 'submit' input, pressing 'enter' in either form
will submit the upper one.
To fix such issues in general, put the dialog into portal, which
put it directly into the body, where it can't interfere with other
elements up the tree. The yew component tree is not affected.
0: https://html.spec.whatwg.org/multipage/forms.html#the-form-element
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
this relies on my previous patch:
https://lore.proxmox.com/yew-devel/20250502124951.3886328-1-d.csapak@proxmox.com/
during my tests, i did not run into any problems, but this change
warrants longer tests, since it's a relatively big change in dom markup.
src/widget/dialog.rs | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/widget/dialog.rs b/src/widget/dialog.rs
index aba77cc..6f492ff 100644
--- a/src/widget/dialog.rs
+++ b/src/widget/dialog.rs
@@ -12,7 +12,7 @@ use yew::prelude::*;
use yew::virtual_dom::{Key, VComp, VNode};
use crate::dom::align::{align_to_viewport, align_to_xy, Point};
-use crate::dom::{get_document, get_window, IntoHtmlElement};
+use crate::dom::{get_body, get_document, get_window, IntoHtmlElement};
use crate::prelude::*;
use crate::props::{AsCssStylesMut, CssStyles};
use crate::widget::{ActionIcon, Panel};
@@ -500,7 +500,7 @@ impl Component for PwtDialog {
let style = props.styles.compile_style_attribute(None);
- html! {
+ let dialog = html! {
<dialog class={"pwt-outer-dialog"} {onpointerdown} aria-label={props.title.clone()} ref={props.node_ref.clone()} {oncancel} {onclose} >
<div class={classes} {style} ref={self.inner_ref.clone()}>
{panel}
@@ -516,7 +516,9 @@ impl Component for PwtDialog {
}
</div>
</dialog>
- }
+ };
+
+ create_portal(dialog, get_body().into())
}
fn rendered(&mut self, ctx: &Context<Self>, first_render: bool) {
--
2.39.5
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
reply other threads:[~2025-05-02 13:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250502130408.3893193-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=yew-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal