소스 검색

Hide extra keyboard shortcuts toggle. Thanks to xet7.

Lauri Ojansivu 1 주 전
부모
커밋
62ad588aa9
2개의 변경된 파일23개의 추가작업 그리고 20개의 파일을 삭제
  1. 2 0
      client/components/boards/boardBody.js
  2. 21 20
      client/components/main/layouts.jade

+ 2 - 0
client/components/boards/boardBody.js

@@ -107,6 +107,7 @@ BlazeComponent.extendComponent({
         el.removeAttribute('tabindex');
         el.removeAttribute('tabindex');
       }
       }
     });
     });
+    /*
     // Add a toggle button for keyboard shortcuts accessibility
     // Add a toggle button for keyboard shortcuts accessibility
     if (!document.getElementById('wekan-shortcuts-toggle')) {
     if (!document.getElementById('wekan-shortcuts-toggle')) {
       const toggleContainer = document.createElement('div');
       const toggleContainer = document.createElement('div');
@@ -136,6 +137,7 @@ BlazeComponent.extendComponent({
         window.toggleWekanShortcuts(e.target.checked);
         window.toggleWekanShortcuts(e.target.checked);
       });
       });
     }
     }
+    */
     // Ensure toggle-buttons, color choices, reactions, renaming, and calendar controls are focusable and have ARIA roles
     // Ensure toggle-buttons, color choices, reactions, renaming, and calendar controls are focusable and have ARIA roles
     document.querySelectorAll('.js-toggle').forEach(function(el) {
     document.querySelectorAll('.js-toggle').forEach(function(el) {
       el.setAttribute('tabindex', '0');
       el.setAttribute('tabindex', '0');

+ 21 - 20
client/components/main/layouts.jade

@@ -1,23 +1,24 @@
-html(lang="{{TAPi18n.getLanguage()}}")
-  head
-  title
-  meta(name="viewport" content="width=device-width, initial-scale=1")
-  meta(http-equiv="X-UA-Compatible" content="IE=edge")
-  //- XXX We should use pathFor in the following `href` to support the case
-    where the application is deployed with a path prefix, but it seems to be
-    difficult to do that cleanly with Blaze -- at least without adding extra
-    packages.
-  link(rel="shortcut icon" type="image/x-icon" href="/favicon.ico")
-  link(rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png")
-  link(rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png")
-  link(rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png")
-  link(rel="manifest" crossOrigin="use-credentials" href="/site.webmanifest")
-  link(rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5")
-  meta(name="apple-mobile-web-app-title" content="Wekan")
-  meta(name="application-name" content="Wekan")
-  meta(name="msapplication-TileColor" content="#00aba9")
-  meta(name="theme-color" content="#ffffff")
-  //link(rel="stylesheet" type="text/css" class="__meteor-css__" href="css/html5-default-theme.css")
+template(name="main")
+  html(lang="{{TAPi18n.getLanguage}}")
+    head
+      title
+      meta(name="viewport" content="width=device-width, initial-scale=1")
+      meta(http-equiv="X-UA-Compatible" content="IE=edge")
+      //- XXX We should use pathFor in the following `href` to support the case
+        where the application is deployed with a path prefix, but it seems to be
+        difficult to do that cleanly with Blaze -- at least without adding extra
+        packages.
+      link(rel="shortcut icon" type="image/x-icon" href="/favicon.ico")
+      link(rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png")
+      link(rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png")
+      link(rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png")
+      link(rel="manifest" crossOrigin="use-credentials" href="/site.webmanifest")
+      link(rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5")
+      meta(name="apple-mobile-web-app-title" content="Wekan")
+      meta(name="application-name" content="Wekan")
+      meta(name="msapplication-TileColor" content="#00aba9")
+      meta(name="theme-color" content="#ffffff")
+      //link(rel="stylesheet" type="text/css" class="__meteor-css__" href="css/html5-default-theme.css")
 
 
 template(name="userFormsLayout")
 template(name="userFormsLayout")
   section.auth-layout
   section.auth-layout