[Dialog] Expose Dialog context

Feature request

Overview

Expose Dialog context so it’s possible to use it in components inside DialogProvider.

Who does this impact? Who is this for?

I want to create a custom Dialog Content component which turns off onPointerDownOutside behaviour and adds click listener on Overlay which closes Dialog so Dialog isn’t closed when clicking Overlay’s scrollbar (https://github.com/radix-ui/primitives/issues/1280).

Raw example:

export function DialogContent(props) {
  const context = useDialogContext(CONTENT_NAME, props.__scopeDialog);

  const onPointerDownOutside = useCallback(event => {
    event.preventDefault();
  }, []);

  const onClickOverlay = useCallback(
    event => {
      // ...implementation
      context.onOpenChange(false);
    },
    [context.onOpenChange],
  );

  return (
    <DialogPortal>
      <DialogOverlay onClick={onClickOverlay}>
        <BaseDialogContent
          {...props}
          onPointerDownOutside={onPointerDownOutside}
        >
          {children}
        </BaseDialogContent>
      </DialogOverlay>
    </DialogPortal>
  );
}

[benoitgrelard]

Hi @lesha1201,

I’ll close this issue and we’ll take a look at #1280

[lesha1201]

@jjenzz From primitive, I expect it to be as much customizable as possible and one of the keys is having access to its internal context. That way it would cover a lot of use-cases (e.g. ability to add lazy-rendering to Dialog.Portal or any other components). It’s impossible to predict many use-cases but from primitive I expect it to be a minimal building block for building more complex components that covers user’s use-cases.

I understand that users still can wrap it in their own context and sync it with the internal context but I think it unnecessary complicates everything.

Dialog already exposes createDialogScope which I think is something internal and it’s not documented anywhere. It could be the same for useDialogContext.

Anyway thank you for the quick replies. I’m going to introduce my own context and wrap in it Dialog for my use-cases. I think it can be closed then.