/*!
 * Copyright (c) 2026-present, Okta, Inc. and/or its affiliates. All rights reserved.
 * The Okta software accompanied by this notice is provided pursuant to the Apache License, Version 2.0 (the "License.")
 *
 * You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
 * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 *
 * See the License for the specific language governing permissions and limitations under the License.
 */
import { type ButtonProps } from "../Buttons/Button.js";
export type FullscreenButtonProps = {
    /**
     * Accessible name for the button. It stays the same whether the region is in fullscreen or not, because the toggle's state is conveyed through `aria-pressed`. Override it when a page has more than one region, so screen reader users can tell the buttons apart (e.g. "Enable fullscreen for the activity chart").
     * @default "Enable fullscreen"
     */
    ariaLabel?: string;
    /**
     * The id of the `FullscreenRegion` this button controls, from `useFullscreenId`. The button can sit anywhere on the page, inside or outside the region.
     */
    fullscreenId: string;
} & Partial<Pick<ButtonProps, "isDisabled" | "size" | "variant">>;
declare const MemoizedFullscreenButton: import("react").MemoExoticComponent<({ ariaLabel, fullscreenId, isDisabled, size, variant, }: FullscreenButtonProps) => import("@emotion/react/jsx-runtime").JSX.Element>;
export { MemoizedFullscreenButton as FullscreenButton };
//# sourceMappingURL=FullscreenButton.d.ts.map