sbourne, 9 months ago

@brucelawson @yatil and @aardrian have been posting about <dialog> just today. They might have weird of wisdom for you!

aardrian, 9 months ago

@sbourne @brucelawson @yatil

It need not be anywhere specific, provided the browser supports the element.

You can test to confirm by playing around with this pen:
https://codepen.io/aardrian/pen/MWPKVbd

brucelawson, 9 months ago

@aardrian Thank you good sir

sbourne, 9 months ago

@aardrian @brucelawson @yatil "words" not "weird" - picked the right audience to muddle through it I guess 😂

aardrian, 9 months ago

@sbourne @brucelawson @yatil
Either word is legit with us.

brucelawson, 9 months ago

@aardrian I was personally overjoyed at the compliment, and now feel a little let-down... @sbourne @yatil

brucelawson, 9 months ago

@aardrian Daft Q, but I'm not seeing where you set "inert on the page container that is a peer to the dialog."

aardrian, 9 months ago

@brucelawson Not a daft question. That statement is simply a lie.

This was me building an experiment prior to a blog post, so I never went back and purged that line (my audience was only ever meant to be me).

I have updated that sentence.

brucelawson, 9 months ago

@aardrian Ah! Thanks old chum. I thought I was losing my residual marble.

aardrian, 9 months ago

@brucelawson Why not both?

brucelawson, 9 months ago

@aardrian Yikes.

marcus, 9 months ago

@brucelawson This sounds like a dialog of the modal/blocking kind. As far as I know that is the cool part about <dialog> when triggered with the .showModal() JS initiator – dialog placement in the DOM does not matter anymore.

brucelawson, 9 months ago

@marcus Cheers, that's what I thought. But I haven't really looked at it for ages, so my memory might be lying

marcus, 9 months ago

@brucelawson In the before times, without inert and just the ARIA roles and states, it was more of a hassle (de-activating DOM subtrees with aria-hidden="true" and inert, but not the one with the dialog yadda yadda)