Bug 1172320 - Browser Content Toolbox should have an accesskey. r=bgrins

This commit is contained in:
Florent Fayolle 2015-06-08 23:10:00 -04:00
Родитель a0c7abbf78
Коммит 257768e507
2 изменённых файлов: 3 добавлений и 1 удалений

Просмотреть файл

@ -543,7 +543,8 @@
observes="devtoolsMenuBroadcaster_BrowserToolbox"
accesskey="&browserToolboxMenu.accesskey;"/>
<menuitem id="menu_browserContentToolbox"
observes="devtoolsMenuBroadcaster_BrowserContentToolbox"/>
observes="devtoolsMenuBroadcaster_BrowserContentToolbox"
accesskey="&browserContentToolboxMenu.accesskey;" />
<menuitem id="menu_browserConsole"
observes="devtoolsMenuBroadcaster_BrowserConsole"
accesskey="&browserConsoleCmd.accesskey;"/>

Просмотреть файл

@ -275,6 +275,7 @@ These should match what Safari and other Apple applications use on OS X Lion. --
- application menu item that opens the browser content toolbox UI in the Tools menu.
- This toolbox allows to debug the chrome of the content process in multiprocess builds. -->
<!ENTITY browserContentToolboxMenu.label "Browser Content Toolbox">
<!ENTITY browserContentToolboxMenu.accesskey "x">
<!ENTITY devToolbarCloseButton.tooltiptext "Close Developer Toolbar">
<!ENTITY devToolbarMenu.label "Developer Toolbar">