Giter VIP home page Giter VIP logo

tabzilla's Introduction

Tabzilla

This is the home of Tabzilla, the universal tab you can add to your website. Below follows simple instructions on how to get, and use Tabzilla.

Upgrading to the new Tabzilla

Before you switch to the new Tabzilla, there are a couple of caveats you need to be aware of.

  • Tabzilla is no longer available as a hosted service. You have to add it to your website using one of the options below.
  • Tabzilla no longer needs any fonts bundled with it so, we are no longer including @font-face declarations for Open Sans in the CSS. NOTE: You can still load the Open-Sans fonts using the Mozilla CDN, or another CDN of your choosing, for example:
@font-face{
    font-family: 'Open Sans Light';
	src: url('https://mozorg.cdn.mozilla.net/media/fonts/OpenSans-Light-webfont.eot?#iefix') format('embedded-opentype'),
         url('https://mozorg.cdn.mozilla.net/media/fonts/OpenSans-Light-webfont.woff') format('woff'),
         url('https://mozorg.cdn.mozilla.net/media/fonts/OpenSans-Light-webfont.ttf') format('truetype');
    font-weight: normal;
    font-style: normal;
}
  • This version of Tabzilla is static and there is no requirement for JavaScript, as such, we no longer inject jQuery.

If you have been relying on any of these assets being included/injected by Tabzilla, you will now have to manually include them on your site.

Bower Package

Do you use Bower to manage your front-end dependencies? Well, then you will be happy to hear that you can install Tabzilla using Bower.

bower install mozilla-tabzilla

That's it! Now you have all the bits you need. Next step, add it to your site.

npm

Already have a package.json and use npm to install dependencies? Well, you can also install Tabzilla using npm. So either add it to your dependency list or, install it using:

npm install mozilla-tabzilla -S

Manual Download

Don't use Bower? No problem, you can download the latest release right here from the releases page.

Once downloaded, extract the package and add the css and media folders to your project.

Using Tabzilla

First step is to add the tabzilla.css file to your main HTML file:

<link rel="stylesheet" type="text/css" href="css/tabzilla.css" media="screen" />

Next, you need to add the following required HTML to your document.

<div id="tabzilla">
    <a href="https://www.mozilla.org/">Mozilla</a>
</div>

Using Tabzilla with Sass

After installing Tabzilla using npm, it is easy to import the styles into your Sass style sheets.

If you're using Gulp, you can require the mozilla-tabzilla module and specify the Tabzilla includePaths using the following snippet:

var gulp = require('gulp');
var sass = require('gulp-sass');
var tabzilla = require('mozilla-tabzilla');

gulp.task('sass', function () {
  gulp.src('*.scss')
    .pipe(sass({
      includePaths: tabzilla.includePaths
    }))
    .pipe(gulp.dest('css'));
});

Then simply call @import "tabzilla"; from within your Sass file to import the Tabzilla styles.

If you're using Grunt, you can require the mozilla-tabzilla module using the following snippet:

var tabzilla = require('mozilla-tabzilla');

module.exports = function (grunt) {
  grunt.loadNpmTasks('grunt-sass');

  grunt.initConfig({
    sass: {
      options: {
        includePaths: [tabzilla.includePaths]
      },
      dist: {
        files: {
          'css/main.css': '*.scss'
        }
      }
    }
  });
};

Changing The Color of the Wordmark

By default the color of the wordmark on Tabzilla is transparent, as below:

Tabzilla with transparent wordmark

You might want to change this to be a solid color instead. You can change the color of the wordmark by adding the following override to your CSS:

#tabzilla:before {
    background-color: #0C99D5;
}

The above will result in the wordmark being displayed as follows:

Tabzilla with custom pink wordmark

[i18n] Right To Left Languages

For right to left languages it makes more sense to have Tabzilla float to the left, as apposed to the right. If you are using Tabzilla in a right to left language website, you need to add the following to the HTML element:

<html dir="rtl">
...

License

MPL-2.0

tabzilla's People

Contributors

alexgibson avatar craigcook avatar darkwing avatar gauthierm avatar glogiotatidis avatar icaaq avatar jpetto avatar pdehaan avatar pmac avatar rossbruniges avatar sgarrity avatar stephaniehobson avatar stephendonner avatar tomer avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

tabzilla's Issues

publish to npm?

Bower is mighty useful, but for those of us whose sites are predominantly deployed as node packages, it would be mighty useful if there was also an npmjs.org entry for tabzilla. That basically requires a package.json file (which can be initialized with the handy npm init command and then interactively filling out all the relevant bits) and having someone call npm publish after that package.json has been created, with a reissue of npm publish every time the current version updates.

Problem Using Content Security Policy in manifest.webapp

Hi all,

Im implementing a webapp for FirefoxOS and now im trying to test it in r2d2b2g but im having some troubles:

My app ask for Ajax jsonp request to a external server to get data, i.e:

$.ajax({
dataType: "jsonp",
url: "http://externalurl.com"
...
});

I tried to allow them through the manifest file, using:

"csp":"default-src *;script-src externalurl.com; options eval-script inline-script;"

and lot of combinations of csp configuration but no one works, it seems like a problem between the schemes app and http.

Which is the best way to allow this kind of request in a FireFox OS App?

Thank you very much.

Pedro

Serbian (sr) translation

"sr" : { // Locale strings for Serbian

// Title Strings
titleMozilla:       "Мозила",
titleProducts:      "Производи",
titleInnovation:    "Иновације",
titleGetInvolved:   "Прикључите се",

// Link Strings
linkMission:        "Мисија",
linkAbout:          "О нама",
linkProjects:       "Пројекти",
linkSupport:        "Подршка",
linkMDN:            "Програмерска мрежа",
linkFirefox:        "Фајерфокс",
linkThunderbird:    "Тандерберд",
linkWebFWD:         "ВебФВД",
linkLabs:           "Лабораторија",
linkVolunteer:      "Волонтирајте",
linkCareers:        "Запослење",
linkFindUs:         "Нађите нас",
linkJoinUs:         "Прикључите се",
linkWebDir:         "Директоријум сајтова",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "Супер награде! Холивудске
    судије! Прикључите се Фајерфокс Фликс такмичењу
    и покажите свету Вашу причу, или 
    гласајте за Ваш омиљени видео!",

}

French localisation (fr)

"fr" : { // Locale strings for French (common)

// Title Strings
titleMozilla: "Mozilla",
titleProducts: "Produits",
titleInnovation: "Innovations",
titleGetInvolved: "Contribuer",

// Link Strings
linkMission: "Mission",
linkAbout: "À propos",
linkProjects: "Projets",
linkSupport: "Support",
linkMDN: "Developer Network",
linkFirefox: "Firefox",
linkThunderbird: "Thunderbird",
linkWebFWD: "WebFWD",
linkLabs: "Labs",
linkVolunteers: "Contribuer",
linkCareers: "Carrière",
linkFindUs: "Nous trouver",
linkJoinUs: "Nous contacter",
linkWebDir: "Plan du site",

// Locale for Firefox Beta Promotions
firefoxBeta: "Téléchargez Firefox Beta, faites nous part de vos remarques et aidez nous à améliorer la prochaine version de Firefox",

}

508/ADA Compliance

Is there any plan to make tabzilla disability friendly? I noticed that on most mozilla websites there is no link to skip over the banner and special needs users are forced to tab through the menu on every page.
See: Techniques for WCAG 2.0 G1

Tamil(IN) Localization

"ta-IN" : { // Locale strings for Tamil India

// Title Strings

titleMozilla:       "மொசில்லா",
titleProducts:      "தயாரிப்புகள்",
titleInnovation:    "புதுமை ",
titleGetInvolved:   "ஈடுபடுங்கள் ",

// Link Strings
linkMission:        "குறிக்கோள் ",
linkAbout:          "எங்களை பற்றி",
linkProjects:       "திட்டங்கள்",
linkSupport:        "ஆதரவு",
linkMDN:            "உருவாக்கிகள் பிணையம் ",
linkFirefox:           "ஃபயர் ஃபாக்சு",
linkThunderbird:    "தண்டர்பேர்டு",
linkWebFWD:         "WebFWD",
linkLabs:           "ஆய்வுக்கூடங்கள் ",
linkVolunteers:     "தொண்டூழியர்கள்",
linkCareers:        "பணித்துறை ",
linkFindUs:         "எங்களைக்காணுங்கள்   ",
linkJoinUs:         "எங்களுடன்சேருங்கள் ",
linkWebDir:         "இணையதள அடைவு ",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "அற்புதமானப் பரிசுகள் ! ஹாலிவுட்
    இயக்குனர்கள் நீதிபதிகளாக..!  பங்கேற்பீர்   Firefox
    Flicks, உலகெங்கும் நடக்கும் வீடியோப் போட்டியில் கலந்து
     நம் வெற்றிக் கதையை உலகிற்கு எடுத்துறைபீர், அல்லது உங்களுக்கு

பிடித்தமானவைக்கு வாக்களிப்பீர்",
}

README.md little corrections

There is some mistakes in README.md file :

  • 2 URL's are incomplete
  • jQuery seems to be needed, but not mentioned in this doc file.

Tabzilla should be in RTL for selected languages

In issue #2 we've hardcoded Tabzilla with dir=ltr in order to make sure the tab won't be affected by the page direction.

Now, when we have support for multiple locales (issue #9), we should redesign the tab so it would be possible to use it on RTL without breaking the display of LTR locales on RTL content pages by reverting the previous hardcoded fix.

By doing so, we should need the following changes:
• Every locale should define its direction, as we are doing in Firefox itself by the &locale.dir; entity. This is important because we need to make sure that LTR locales, such as English, French etc. will be displayed well on RTL pages as well as LTR pages.
• We should decide what should be flipped on RTL locale tabs. The easiest way is to mirror everything, but by doing so we will end up with some usability problems as the locale picker, for example, would be switched to the other side of the page, so if people will switch to an RTL language by mistake they might be unable to locate the language picker again in order to switch back.
• We should add a display class to RTL which would be applied after we switch locales.

Spanish localization

Hi,

We are implementing tabzilla in the new Mozilla Hispano design, but we need the text to be localizable in Spanish.

This involves title names, some urls are en-US hard-coded, and link names. Also it would be great to be able to have the search box to search also in mozilla-hispano.org domain.

Thanks.

Hebrew translation

"he" : { // Locale strings for Hebrew

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "מוצרים",
titleInnovation:    "חדשנות",
titleGetInvolved:   "היו מעורבים",

// Link Strings
linkMission:        "משימה",
linkAbout:          "אודות",
linkProjects:       "מיזמים",
linkSupport:        "תמיכה",
linkMDN:            "Developer Network",
linkFirefox:        "Firefox",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "Labs",
linkVolunteers:     "מתנדבים",
linkCareers:        "קריירה",
linkFindUs:         "מצאו אותנו",
linkJoinUs:         "הצטרפו אלינו",
linkWebDir:         "מדריך אתרים",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "פרסים גדולים! שופטים מהוליווד! סימני קריאה! 

היכנסו אל Firefox Flicks, תחרות וידאו עולמית שמטרתה לספר את סיפורנו,
או הצביעו למועדפים עליכם!",
}

Hindi localisation of Tabzilla

"hi" : { // Locale strings for English

// Title Strings
titleMozilla:       "मोज़िल्ला",
titleProducts:      "उत्पाद",
titleInnovation:    "नवोन्मेष",
titleGetInvolved:   "शामिल हो",

// Link Strings
linkMission:        "उद्देश्य",
linkAbout:          "विवरण",
linkProjects:       "परियोजना",
linkSupport:        "सहायता",
linkMDN:            "डेवेलोपेर समूह",
linkFirefox:        "फायरफ़ॉक्स",
linkThunderbird:    "थंडरबर्ड ",
linkWebFWD:         "WebFWD",
linkLabs:           "प्रयोगशाला",
linkWebmaker:       "Webmaker"
linkVolunteer:      "स्वयंसेवक",
linkCareers:        "रोज़गार",
linkFindUs:         "हम से मिले",
linkJoinUs:         "हम से जुड़े",
linkWebDir:         "वेबसाइट निर्देशिका",

// Locale for the Promotional Contents
promoLink:          "फायरफॉक्स बीटा डाउनलोड करे,
    प्रतिक्रिया देकर फायरफॉक्स के अगले संस्करण को
    और भी अद्भुत बनाने में सहयोग करे."

},

Malay (ms) Translation

"ms" : { // Locale strings for Bahasa Malaysia / Malay

// Title Strings
titleMozilla: "Mozilla",
titleProducts: "Produk",
titleInnovation: "Innovasi",
titleGetInvolved: "Ayuh Bergabung!",

// Link Strings
linkMission: "Misi",
linkAbout: "Tentang Kami",
linkProjects: "Projek",
linkSupport: "Sokongan",
linkMDN: "Developer Network",
linkFirefox: "Firefox",
linkThunderbird: "Thunderbird",
linkWebFWD: "WebFWD",
linkLabs: "Labs",
linkVolunteers: "Sukarelawan",
linkCareers: "Kareer",
linkFindUs: "Cari Kami",
linkJoinUs: "Sertai Kami",
linkWebDir: "Peta Laman",

// Locale for Firefox Beta Promotions
firefoxBeta: "Muat turun Firefox Beta, berikan maklum balas dan bantu untuk menjadikan versi daripada Firefox malah lebih hebat!",

}

open sans is getting rejected in firefox over "too large a kern table"

Seeing the following errors when using tabzilla:

downloadable font: kern: Too large subtable., table discarded (font-family: "Open Sans" style:normal weight:bold stretch:normal src index:1) source: https://mozorg.cdn.mozilla.net/media/fonts/OpenSans-Bold-webfont.woff
downloadable font: kern: Too large subtable., table discarded (font-family: "Open Sans" style:normal weight:normal stretch:normal src index:1) source: https://mozorg.cdn.mozilla.net/media/fonts/OpenSans-Regular-webfont.woff

Remove absolute references to images in CSS

Currently there are two absolute image paths in the CSS. It'd be super neat if these were relative so that we can include tabzilla via bower or npm and not have to adjust our directory structure to have a top level /media/ directory:

  1. background-image: url('/media/img/tabzilla-static.png'); (via /css/tabzilla.css:13)
  2. background-image: url("/media/img/tabzilla-static-high-res.png"); (via /css/tabzilla.css:19)

Burmese Translation

"my" : { // Locale strings for Burmese

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "ထုတ်ကုန်များ",
titleInnovation:    "တီထွင်ဆန်းသစ်ချက်များ",
titleGetInvolved:   "ပါ၀င်ဆောင်ရွက်ရန်",

// Link Strings
linkMission:        "ရည်မှန်းချက်",
linkAbout:          "အကြောင်းအရာ",
linkProjects:       "စီမံကိန်းများ",
linkSupport:        "ထောက်ပံ့ကူညီရန်",
linkMDN:            "Developer Network",
linkFirefox:        "မြီးမြေခွေး",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "Labs",
linkWebmaker:       "Webmaker"
linkVolunteer:     " စေတနာ့၀န်ထမ်းများ",
linkCareers:        "သက်မွေး၀မ်းကျောင်း",
linkFindUs:         "ရှာရန်",
linkJoinUs:         "ပူးပေါင်းပါ၀င်ဆောင်ရွက်ရန်",
linkWebDir:         "ဝဘ်ဆိုက် လမ်းညွှန်",

// Locale for the Promotional Contents
promoLink:         "Firefox Beta အား Download ချ၍ တွေ့ရှိမှုများကို တုံ့ပြန်ချက်ပေး၍ နောက်အသစ်ထွက်ရှိလာမည့်  Firefox အား ပိုမိုကောင်းမွန်လာစေရန် ကူညီပေးပါရန်"

},

Add README and gulpfile.js to bower ignore?

Currently the /bower.json ignore array looks like this:

  "ignore": [
    "docs-assets",
    "less",
    "node_modules",
    ".gitignore",
    "bower.json",
    "Gruntfile.js",
    "index.html",
    "package.json"
  ],

Not sure if we want to add the README.md (1.7KB) and the gulpfile.js (620B) to the ignore list. We can probably just change the existing Gruntfile.js with gulpfile.js since it looks like we introduced Gulp in #54 PR.

➜  tabzillaz  bower i mozilla-tabzilla
bower mozilla-tabzilla#*        cached git://github.com/mozilla/tabzilla.git#0.3.0
bower mozilla-tabzilla#*      validate 0.3.0 against git://github.com/mozilla/tabzilla.git#*
bower mozilla-tabzilla#~0.3.0  install mozilla-tabzilla#0.3.0

mozilla-tabzilla#0.3.0 bower_components/mozilla-tabzilla

➜  tabzillaz  ls -lash bower_components/mozilla-tabzilla
total 32
0 drwxr-xr-x  8 pdehaan  staff   272B Aug  4 13:36 .
0 drwxr-xr-x  3 pdehaan  staff   102B Aug  4 13:36 ..
8 -rw-r--r--  1 pdehaan  staff   862B Aug  4 13:36 .bower.json
8 -rw-r--r--  1 pdehaan  staff   1.7K Jul 15 01:27 README.md
8 -rw-r--r--  1 pdehaan  staff   574B Jul 15 01:27 bower.json
0 drwxr-xr-x  3 pdehaan  staff   102B Jul 15 01:27 css
8 -rw-r--r--  1 pdehaan  staff   620B Jul 15 01:27 gulpfile.js
0 drwxr-xr-x  3 pdehaan  staff   102B Jul 29 17:43 media

Tamil(IN) Localization

"ta-IN" : { // Locale strings for Tamil India

// Title Strings

titleMozilla:       "மொசில்லா",
titleProducts:      "தயாரிப்புகள்",
titleInnovation:    "புதுமை ",
titleGetInvolved:   "ஈடுபடுங்கள் ",

// Link Strings
linkMission:        "குறிக்கோள் ",
linkAbout:          "எங்களை பற்றி",
linkProjects:       "திட்டங்கள்",
linkSupport:        "ஆதரவு",
linkMDN:            "உருவாக்கிகள் பிணையம் ",
linkFirefox:           "ஃபயர் ஃபாக்சு",
linkThunderbird:    "தண்டர்பேர்டு",
linkWebFWD:         "WebFWD",
linkLabs:           "ஆய்வுக்கூடங்கள் ",
linkVolunteers:     "தொண்டூழியர்கள்",
linkCareers:        "பணித்துறை ",
linkFindUs:         "எங்களைக்காணுங்கள்   ",
linkJoinUs:         "எங்களுடன்சேருங்கள் ",
linkWebDir:         "இணையதள அடைவு ",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "அற்புதமானப் பரிசுகள் ! ஹாலிவுட்
    இயக்குனர்கள் நீதிபதிகளாக..!  பங்கேற்பீர்   Firefox
    Flicks, உலகெங்கும் நடக்கும் வீடியோப் போட்டியில் கலந்து
     நம் வெற்றிக் கதையை உலகிற்கு எடுத்துறைபீர், அல்லது உங்களுக்கு

பிடித்தமானவைக்கு வாக்களிப்பீர்",
}

Chinese Traditional (Taiwan) Localization

"zh-TW" : { // Locale strings for Chinese Traditional (Taiwan)

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "產品",
titleInnovation:    "創新",
titleGetInvolved:   "參與其中",

// Link Strings
linkMission:        "使命",
linkAbout:          "關於",
linkProjects:       "專案",
linkSupport:        "技術資源",
linkMDN:            "開發者網路",
linkFirefox:        "Firefox",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "實驗室",
linkVolunteers:     "志工",
linkCareers:        "工作機會",
linkFindUs:         "尋找我們",
linkJoinUs:         "加入我們",
linkWebDir:         "網站目錄",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "超棒的大獎、好萊塢評審、讓眾人驚嘆!
        請參加 Firefox Flicks,一個讓您述說我
        們故事的全球性短片競賽。您也可以參加
        投出您最愛的短片!",

}

Attribute the localization work in a file from the source code tree

Please give credits to the people who contributed with localization to Tabzilla in a file that is distributed along with the source code. This is required by MPL, the license for the source code.

Suggestions:

  • comments in /media/locale.js
  • section in a separate file like /THANKS(.md) or /CREDITS(.md)

Add includePaths support for easier Sass usage

We're trying to use this module w/ Sass and it'd be nice if there was includePaths support.

See node-normalize-scss, node-bourbon, and node-neat.

This way we could do something like @import "css/tabzilla"; instead of @import "../../../node_modules/mozilla-tabzilla/css/tabzilla";.

Although we'd still need to do some build step trickery to convert "css/tabzilla.css" to "css/_tabzilla.scss" to make it easier to use w/ Sass.


For reference, here's my current _vendor.scss file:

@import 'normalize';
@import '../../../../node_modules/mozilla-tabzilla/css/tabzilla';

... where I need to have a build script to rename /css/tabzilla.css to /css/_tabzilla.scss.

gulp.task('tabzilla-sass', function () {
  gulp.src('../../../../node_modules/mozilla-tabzilla/css/tabzilla.css')
    .pipe(rename('_tabzilla.scss'))
    .pipe(gulp.dest('../../../../node_modules/mozilla-tabzilla/css/'));
});

Macedonian (mk) translation

"en" : { // Locale strings for English

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "Производи",
titleInnovation:    "Иновација",
titleGetInvolved:   "Приклучете се",

// Link Strings
linkMission:        "Мисија",
linkAbout:          "За нас",
linkProjects:       "Проекти",
linkSupport:        "Поддршка",
linkMDN:            "Мрежа на развивачи",
linkFirefox:        "Firefox",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "Labs",
linkWebmaker:       "Webmaker"
linkVolunteer:      "Волонтирање",
linkCareers:        "Вработување",
linkFindUs:         "Пронајдете нè",
linkJoinUs:         "Приклучете се",
linkWebDir:         "Веб-директориум",

// Locale for the Promotional Contents
promoLink:          "Преземете го Firefox Beta, споделете искуства и помогнете следната верзија на Firefox да биде уште подобра."

},

Bahasa Indonesia [id] Translation

"id" : { // Locale strings for Bahasa Indonesia

// Title Strings
titleMozilla: "Mozilla",
titleProducts: "Produk",
titleInnovation: "Inovasi",
titleGetInvolved: "Ikut Berperan",

// Link Strings
linkMission: "Misi",
linkAbout: "Tentang Kami",
linkProjects: "Proyek",
linkSupport: "Dukungan",
linkMDN: "Jaringan Pengembang",
linkFirefox: "Firefox",
linkThunderbird: "Thunderbird",
linkWebFWD: "WebFWD",
linkLabs: "Labs",
linkVolunteers: "Sukarelawan",
linkCareers: "Karier",
linkFindUs: "Temukan Kami",
linkJoinUs: "Bergabung Dengan Kami",
linkWebDir: "Direktori Situs Web",

// Locale for Firefox Beta Promotions
firefoxBeta: "Unduh Firefox Beta, berikan umpan balik dan bantu kami untuk menjadikan Firefox lebih baik!",

}

Version numbering of the whole (or parts) of tabzilla

In conjunction with my work on #25 I think it would be awesome if we could start versioning tabzilla as a whole.

I suspect most Mozilla sites that will reference the minified version (which will soon hopefully live on a snappy CDN) will use the "latest" version but for those who want optimal speed (i.e. cache-control = max) will want to use a version numbered URL. Like google does: http://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js

Should this repo be deprecated?

We discussed this a bit in #85, but now that the new brand guidelines don't allow the mozilla wordmark being placed inside a container (such as the curved Tabzilla tab), updating this repo with the new wordmark might be slightly redundant. Sites can just include the wordmark where appropriate according to the guidelines, and it might not make sense to have a shared piece of CSS defining where it appears as navigation also varies site to site.

Thoughts @craigcook @jpetto @pmac ?

I feel like we should probably make some kind of decision here soon, to at least provide some sort of guidance as to what people should do.

Dutch (nl) translation

"nl" : { // Locale strings for Dutch

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "Producten",
titleInnovation:    "Innovatie",
titleGetInvolved:   "Doe mee",

// Link Strings
linkMission:        "Missie",
linkAbout:          "Over",
linkProjects:       "Projecten",
linkSupport:        "Support",
linkMDN:            "Ontwikkelaarsnetwerk",
linkFirefox:        "Firefox",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "Labs",
linkVolunteers:     "Vrijwilligers",
linkCareers:        "Vacatures",
linkFindUs:         "Vind ons",
linkJoinUs:         "Meedoen",
linkWebDir:         "Website overzicht",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "Grote prijzen! Hollywood
    jury! Uitroeptekens! Bekijk Firefox
    Flicks, de wereldwijde videowedstrijd om ons
    verhaal te vertellen, of stem op uw favoriet!",

}

The content inside of #tabzilla-contents should not recieve focus when tabzilla is closed

If using a keyboard all the links and input-fields inside #tabzilla-contents are focusable, this is really confusing when using a keyboard to navigate sites that has the tabzilla included, for example if a user clicks tab to skip to the next link nothing will appear to happen on all of these link and input-fileds.

Use display:none on #tabzilla-content if tabzilla is closed solves this problem. Users that uses screenreaders should also be informed that the tabzilla is open, therefor when tabzilla is open a aria-haspopup [1] attribute should be set to true with a aria-owns [2] attribute that points to #tabzilla-contents

[1]. http://www.w3.org/TR/wai-aria/states_and_properties#aria-haspopup
[2]. http://www.w3.org/TR/wai-aria/states_and_properties#aria-owns

HTTP ERROR 500 after update plugin!

Every time I try to access (forexample) mywebsite.com.au/wp-admin it gives me the following message. I have cleared website history and reinstalled Chrome.

The mywesbite .com.au page isn’t working

mywebsite.com.au is currently unable to handle this request.
HTTP ERROR 500

this only happened after I finished updating your plugin on wordpress! please help

Improve accessibility

Reporting this in one of our Mozilla Hispano web developers behalf:

To improve Tabzilla accessibility I think it's important to separate the content (html) from the logic (js), so I propose a modification that won't embed the html via javascript.

Maybe having a service from http://www.mozilla.org/tabzilla/media/content.en.html that returns the content served now via js, that content would be used by community sites, using a cron or other ways to retrieve an updated copy which includes the html.

This way will also help to have the content localized for each language (content.es.html, content.fr.html...)

The ’ character get incorrectly rendered when jingo minified.

Tabzilla text contains the ’ character in the phraze

"Wherever you’re going in the Mozilla Web universe, this is your starting place. Happy exploring!"

which is silently translated to

"Wherever you???re going in the Mozilla Web universe, this is your starting place. Happy exploring!"

when tabzilla.js gets jingo minified. Since jingo is the default css/js compressor we use in playdoh this can break our tabzilla appearance.

Replacing ’ with ’ fixes the problem.

moz-box-sizing breaks tabzilla promo

On the webfwd site the * { -moz-box-sizing: border-box; } rule is set and this causes the tabzilla promo to display it's contents incorrectly i.e. the height collapses to 130px and causes the text to overlap the image. https://webfwd.org/

Spanish localization

"es" : { // Locale strings for Spanish (common)

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "Productos",
titleInnovation:    "Innovación",
titleGetInvolved:   "Involúcrate",

// Link Strings
linkMission:        "Misión",
linkAbout:          "Acerca de",
linkProjects:       "Proyectos",
linkSupport:        "Asistencia",
linkMDN:            "Developer Network",
linkFirefox:        "Firefox",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "Labs",
linkVolunteers:     "Voluntarios",
linkCareers:        "Trabajos",
linkFindUs:         "Encuéntranos",
linkJoinUs:         "Únete",
linkWebDir:         "Directorio del sitio",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "¡Grandes premios! ¡Un jurado de estrellas de Hollywood! ¡Participa en Firefox Flicks, el concurso mundial de vídeos para contar nuestra historia, o vota a tus favoritos!",

}

Slovenian (sl) localization

"en" : { // Locale strings for Slovenian

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "Izdelki",
titleInnovation:    "Inovacije",
titleGetInvolved:   "Sodelujte",

// Link Strings
linkMission:        "Poslanstvo",
linkAbout:          "Predstavitev",
linkProjects:       "Projekti",
linkSupport:        "Podpora",
linkMDN:            "Za razvijalce",
linkFirefox:        "Firefox",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "Labs",
linkVolunteer:      "Prostovoljci",
linkCareers:        "Zaposlitev",
linkFindUs:         "Kje smo?",
linkJoinUs:         "Pridružite se",
linkWebDir:         "Imenik strani",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "Lepe nagrade! Sodniki 
    iz Hollywooda! Klicaji! Sodelujte v Firefox Flicks,
    svetovnem nagradnem tekmovanju,
    s svojo zgodbo ali glasujte za svoje favorite!",

}

License

What is the license for the code of Tabzilla?

Frisian (fy-NL) translation

"fy-NL" : { // Locale strings for Frisian

// Title Strings
titleMozilla:       "Mozilla",
titleProducts:      "Produkten",
titleInnovation:    "Ynnovaasje",
titleGetInvolved:   "Doch mei",

// Link Strings
linkMission:        "Missy",
linkAbout:          "Oer",
linkProjects:       "Projekten",
linkSupport:        "Stipe",
linkMDN:            "Untwikkelersnetwurk",
linkFirefox:        "Firefox",
linkThunderbird:    "Thunderbird",
linkWebFWD:         "WebFWD",
linkLabs:           "Labs",
linkVolunteers:     "Frijwilligers",
linkCareers:        "Fakatueres",
linkFindUs:         "Fyn ús",
linkJoinUs:         "Meidwaan",
linkWebDir:         "Website oersjoch",

// Locale for Firefox Flicks Promotions
firefoxFlicks:      "Grutte prizen! Hollywood
    sjuery! Utroptekens! Besjoch Firefox
    Flicks, de wrâldwide fideowedstryd om ús
    ferhaal te fertellen, of stim op jo favoryt!",

}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.