See our page on Typography for more info and examples.Īdditionally, there are two different scales available: a standard scale with large titles, appropriate for most general websites (like marketing sites, blogs, etc) and a condensed scale with smaller sizes more suitable for web applications.
Scale sizes and line heights are defined as part of the brand theme, and each brand has a slightly different scale. Protocol uses a modular type scale with a range of predefined font sizes to maintain consistency and avoid sizing text willy nilly in designs. If you want to use a SCSS variable in multiple files, you need to re-declare it or import it to those files.) (Note: SCSS variables do not cascade like CSS variables because they are compiled away in the build step. If you want to produce a Firefox-branded website you'll need to compile the Protocol SCSS and change the $brand-theme variable: $brand-theme: 'firefox' We still recommend doing your own compiling so you can import just the components you need. Protocol defaults to the Mozilla brand “out of the box.” If you use the packaged, pre-compiled CSS, you’ll have everything you need for a Mozilla-branded website without needing to compile the SCSS yourself. (Note: this kind of theming is also possible with custom properties in native CSS, but Protocol still needs to support older browsers so we use SCSS variables.) These variables are collected into maps and we then use functions in SCSS to swap to a different map based on a single theme variable: $brand-theme: 'mozilla' Our CSS framework achieves the different themes by assigning variables to several style properties, then drawing from different sets of variables to apply different styling based on which brand is represented on the page. The Firefox brand uses the Metropolis typeface and is generally more colorful overall. The Mozilla brand is distinguished by the Zilla Slab typeface and a limited color palette, mostly black and white. Use the Tools menu to access to the CookieKeeper interface.Protocol supports two distinct brands: Mozilla and Firefox. Extract the file cookiekeeper.kmm located in the kmeleon sub-folder, to the previously created macros directory
Then open the folder extensions and with your favorite ZIP file manager, open the file.Create a new folder named macros if it do not already exists.Go to your K-Meleon profil directory C:\Users\\AppData\Roaming\K-Meleon\.Force the module installation by clicking on the grey button "Add to Firefox", then "Install Anyway".This support is minimal, for example, the dynamic menu is not implemented. For example, this value work: Mozilla/5.0 (Linux X11 rv:24.9) Gecko/20100101 Firefox/45.0 (Pale Moon) Note for K-Meleon users: This is the first release of CookieKeeper with a K-Meleon support.
To be able to install CookieKeeper you must update in the "about:config" the option. with a compatible Firefox version. Note for Palemoon users: By default on Palemoon 26.1 you may see that CookieKeeper 1.9 is not compatible with Firefox 24.9. For version 1.9.0 See the changelog here: Supported Mozilla based applications: I have finally rewrote the whole code, based on the Mozilla cookie window. This add-on has started as an update of CookieCuller for newer Firefox version. Keep the cookies you want, delete the rest.