NavNav provides a ton of CSS, jQuery, and JavaScript responsive navigation examples, demos, and tutorials from all over the web.
metisMenu offers a lot of options to tweak layout and usage. The plugin provides options for
@font-face is a CSS at-rule used to define custom fonts for use on web pages. It allows web designers and developers to specify downloadable fonts that can be used to render text on their websites, regardless of whether the font is installed on the user’s device.
There are three common issues regarding text rendering on browsers. And the goal always is to reduce or at least minimize the text reflow.
FOUT stands for „Flash of Unstyled Text.“ It’s a phenomenon that occurs when using web fonts in CSS. When a web page is loading, the browser might initially render text using a fallback font while waiting for the web font to download and apply. This results in a momentary flash where the text appears in the fallback font before switching to the desired web font.
FOUT can be visually disruptive, especially if the fallback font differs significantly from the intended web font in terms of style or size. To mitigate FOUT, web developers often use techniques such as font loading strategies (like using the font-display property in CSS) or server-side rendering to ensure that the desired web font is loaded and applied as quickly as possible to minimize or eliminate the flash of unstyled text.
FOIT stands for „Flash of Invisible Text.“ It’s another phenomenon related to web fonts in CSS. Unlike FOUT, where fallback text is briefly visible before the web font loads, FOIT occurs when the browser hides text until the web font is fully loaded and ready to be applied.
When FOIT happens, the text remains invisible until the browser has downloaded the web font. This can result in a delay in displaying text content on the webpage, which might lead to a poor user experience.
To address FOIT, web developers sometimes use techniques such as font loading strategies (like preloading fonts or using the font-display property) to ensure that text content remains visible while waiting for web fonts to load. These techniques aim to balance the trade-off between the performance benefits of font loading and the user experience of text visibility.
„FOFT“ stands for „Flash of Faux Text.“ This term describes a phenomenon similar to FOUT (Flash of Unstyled Text) but specifically occurs when using synthetic fonts, such as system fonts or web-safe fonts, instead of custom web fonts.
In FOFT, when a web page is loading, the browser may initially render text using a generic font (like Arial or Times New Roman) before switching to the specified font once it has fully loaded. This switch can result in a brief flash where the text appears in the generic font before being replaced with the intended font, causing a disruption in the visual appearance of the text.
To mitigate FOFT, developers can employ similar techniques used to address FOUT, such as optimizing font loading strategies or utilizing font preloading techniques to ensure a smoother transition from the generic font to the specified font. Additionally, choosing system fonts or web-safe fonts that closely resemble the desired custom font can help reduce the visibility of FOFT.
Use the CSS font loading API. Not supported in all browsers yet (MDN, W3C). You can call document.fonts to get a FontFaceSet object.
check(fontSpec) – returns whether all fonts in the given font list have been loaded and are available. The fontSpec uses the CSS shorthand syntax for fonts.document.fonts.check('bold 16px Roboto'); // true or falsedocument.fonts.ready – returns a Promise indicating that font loading and layout operations are done.|
1 2 3 4 5 6 7 8 9 10 |
alert('Roboto loaded? ' + document.fonts.check('1em Roboto')); // false document.fonts.ready.then(function () { alert('All fonts in use by visible text have loaded.'); alert('Roboto loaded? ' + document.fonts.check('1em Roboto')); // true }); document.fonts.onloadingdone = function (fontFaceSetEvent) { alert('onloadingdone we have ' + fontFaceSetEvent.fontfaces.length + ' font faces loaded'); }; |
Use Font Face Observer – its a small @font-face loader and monitor compatible with any web font service. It will monitor when a web font is applied to the page and notify you. It does not limit you in any way in where, when, or how you load your web fonts. Unlike the Web Font Loader Font Face Observer uses scroll events to detect font loads efficiently and with minimum overhead.
|
1 2 3 4 5 6 7 8 9 |
var font = new FontFaceObserver('My Family', { weight: 400 }); font.load().then(function () { console.log('Font is available'); }, function () { console.log('Font is not available'); }); |
Use jQuery-FontSpy.js, works by checking the change in width of a string.
|
1 2 3 4 5 6 7 8 9 |
fontSpy('My Icons', { glyphs: '\ue81a\ue82d\ue823', success: function() { //alert("My Icons loaded successfully"); }, failure: function() { //alert("My Icons failed to load"); } }); |
Use Webfont Loader, if loading fonts from Typekit , Fonts.com, Google, Fontdeck or custom location.
This introduces the following events:
loading – This event is triggered when all fonts have been requested.active – This event is triggered when the fonts have rendered.inactive – This event is triggered when the browser does not support linked fonts or if none of the fonts could be loaded.fontloading – This event is triggered once for each font that’s loaded.fontactive – This event is triggered once for each font that renders.fontinactive – This event is triggered if the font can’t be loaded.|
1 2 3 4 5 6 7 8 |
<script src="https://ajax.googleapis.com/ajax/libs/webfont/1.6.16/webfont.js"></script> <script> WebFont.load({ google: { families: ['Droid Sans', 'Droid Serif'] } }); </script> |
BackgroundCheck automatically switches to a darker or a lighter version of an element depending on the brightness of images behind it.
Pretty amazing and useful, when doing long one-pagers with switching section backgrounds and navigation elements hovering above them.
|
1 2 3 4 5 6 7 8 9 10 11 |
p.background--light { color: black; } p.background--dark { color: white; } p.background--complex { color: gray; } |
|
1 2 3 4 5 6 7 8 9 10 |
// Check all elements with a .target class against all images on a page BackgroundCheck.init({ targets: '.target' }); // Specific images BackgroundCheck.init({ targets: '.target', images: '.thumbnails' }); |
Unlike other i18n/l10n libraries, webL10n supports:
l10n-* attributes are automatically translated when the document is loaded;%s tokens;
SPLIT PANES / DOCKER allow you to display multiple areas, either side by side or one on top of each other. Nested layouts are often part of it. By dragging a divider that appears between the areas, the user can specify how much of the total width / height goes to each area.
I have been building a backend interface in the past weeks, that forced me to look into ways to organize the workspace more efficiently . I could code my own splitter, but is not a priority right now and makes no sense to always reinvent the wheel :)
Here some of the options out there…
This uses the jQuery UI draggable component and provides limited options :)
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
$('.splitter').draggable({ axis: 'x', containment: '#content', distance: 0, drag: function(event, ui) { var width = $('#content').width(); $('#content .leftpane').css({ width: ui.position.left + 'px' }); $('#content .rightpane').css({ left: ui.position.left + 1 + 'px', width: (width - ui.position.left + 1) + 'px' }); }, refreshPositions: true, scroll: false }); |
Zombie.js is a lightweight framework for testing client-side JavaScript code in a simulated environment. No browser required.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 |
const Browser = require('zombie'); // We're going to make requests to http://example.com/signup // Which will be routed to our test server localhost:3000 Browser.localhost('example.com', 3000); describe('User visits signup page', function() { const browser = new Browser(); before(function(done) { browser.visit('/signup', done); }); describe('submits form', function() { before(function(done) { browser .fill('email', 'zombie@underworld.dead') .fill('password', 'eat-the-living') .pressButton('Sign Me Up!', done); }); it('should be successful', function() { browser.assert.success(); }); it('should see welcome page', function() { browser.assert.text('title', 'Welcome To Brains Depot'); }); }); }); |
