2018-07-31 22:30:17 +03:00
|
|
|
/* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
|
|
|
|
/* vim: set ts=8 sts=2 et sw=2 tw=80: */
|
|
|
|
/* This Source Code Form is subject to the terms of the Mozilla Public
|
|
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
|
|
|
|
|
|
|
|
#ifndef mozilla_dom_XULMenuElement_h
|
|
|
|
#define mozilla_dom_XULMenuElement_h
|
|
|
|
|
Bug 1805414 - Remove nsMenuFrame and nsMenuParent. r=smaug,Jamie,desktop-theme-reviewers,settings-reviewers,dao
Move most the event handling stuff to the DOM. I've left nsMenuBarFrame
for now, but I will be removing that in the future.
The basic set up is:
* nsMenuParent becomes XULMenuParentElement (menubar or popup, manages
the current active menu item)
* nsMenuFrame -> XULButtonElements that return true for IsMenu().
Can't use XULMenuElement because of <button type=menu>, which
behaves like a, well, menu.
This makes the a11y events for menus (DOMMenuItem{Active,Inactive}) make
sense (before that we were firing duplicate Inactive events etc, and the
event order was rather suspicious).
Differential Revision: https://phabricator.services.mozilla.com/D164210
2023-01-04 22:01:13 +03:00
|
|
|
#include "XULButtonElement.h"
|
|
|
|
#include "nsINode.h"
|
2018-07-31 22:30:17 +03:00
|
|
|
#include "nsXULElement.h"
|
|
|
|
|
2022-05-09 23:41:21 +03:00
|
|
|
namespace mozilla::dom {
|
2018-07-31 22:30:17 +03:00
|
|
|
|
|
|
|
class KeyboardEvent;
|
|
|
|
|
Bug 1805414 - Remove nsMenuFrame and nsMenuParent. r=smaug,Jamie,desktop-theme-reviewers,settings-reviewers,dao
Move most the event handling stuff to the DOM. I've left nsMenuBarFrame
for now, but I will be removing that in the future.
The basic set up is:
* nsMenuParent becomes XULMenuParentElement (menubar or popup, manages
the current active menu item)
* nsMenuFrame -> XULButtonElements that return true for IsMenu().
Can't use XULMenuElement because of <button type=menu>, which
behaves like a, well, menu.
This makes the a11y events for menus (DOMMenuItem{Active,Inactive}) make
sense (before that we were firing duplicate Inactive events etc, and the
event order was rather suspicious).
Differential Revision: https://phabricator.services.mozilla.com/D164210
2023-01-04 22:01:13 +03:00
|
|
|
class XULMenuElement final : public XULButtonElement {
|
2018-07-31 22:30:17 +03:00
|
|
|
public:
|
2018-09-21 23:45:49 +03:00
|
|
|
explicit XULMenuElement(already_AddRefed<mozilla::dom::NodeInfo>&& aNodeInfo)
|
Bug 1805414 - Remove nsMenuFrame and nsMenuParent. r=smaug,Jamie,desktop-theme-reviewers,settings-reviewers,dao
Move most the event handling stuff to the DOM. I've left nsMenuBarFrame
for now, but I will be removing that in the future.
The basic set up is:
* nsMenuParent becomes XULMenuParentElement (menubar or popup, manages
the current active menu item)
* nsMenuFrame -> XULButtonElements that return true for IsMenu().
Can't use XULMenuElement because of <button type=menu>, which
behaves like a, well, menu.
This makes the a11y events for menus (DOMMenuItem{Active,Inactive}) make
sense (before that we were firing duplicate Inactive events etc, and the
event order was rather suspicious).
Differential Revision: https://phabricator.services.mozilla.com/D164210
2023-01-04 22:01:13 +03:00
|
|
|
: XULButtonElement(std::move(aNodeInfo)) {}
|
2018-07-31 22:30:17 +03:00
|
|
|
|
Bug 1805414 - Remove nsMenuFrame and nsMenuParent. r=smaug,Jamie,desktop-theme-reviewers,settings-reviewers,dao
Move most the event handling stuff to the DOM. I've left nsMenuBarFrame
for now, but I will be removing that in the future.
The basic set up is:
* nsMenuParent becomes XULMenuParentElement (menubar or popup, manages
the current active menu item)
* nsMenuFrame -> XULButtonElements that return true for IsMenu().
Can't use XULMenuElement because of <button type=menu>, which
behaves like a, well, menu.
This makes the a11y events for menus (DOMMenuItem{Active,Inactive}) make
sense (before that we were firing duplicate Inactive events etc, and the
event order was rather suspicious).
Differential Revision: https://phabricator.services.mozilla.com/D164210
2023-01-04 22:01:13 +03:00
|
|
|
MOZ_CAN_RUN_SCRIPT void SetActiveMenuChild(Element*);
|
|
|
|
Element* GetActiveMenuChild();
|
|
|
|
|
|
|
|
NS_IMPL_FROMNODE_HELPER(XULMenuElement,
|
|
|
|
IsAnyOfXULElements(nsGkAtoms::menu,
|
|
|
|
nsGkAtoms::menulist));
|
2018-07-31 22:30:17 +03:00
|
|
|
|
|
|
|
private:
|
2020-02-20 18:54:52 +03:00
|
|
|
virtual ~XULMenuElement() = default;
|
2018-07-31 22:30:17 +03:00
|
|
|
JSObject* WrapNode(JSContext* aCx, JS::Handle<JSObject*> aGivenProto) final;
|
|
|
|
};
|
|
|
|
|
2022-05-09 23:41:21 +03:00
|
|
|
} // namespace mozilla::dom
|
2018-07-31 22:30:17 +03:00
|
|
|
|
|
|
|
#endif // XULMenuElement_h
|