I built something with #A-Frame in 2 days (and you can too) - Mozilla Hacks - the Web developer blog
▻https://hacks.mozilla.org/2017/09/i-built-something-with-a-frame-in-2-days-and-you-can-too
►https://aframe.io
▻https://github.com/donmccurdy/aframe-extras
#3D
je me suis lancé dans AFrame il y a quelques jours et en effet c’est aussi chouette que le HTML et le SVG, voire plus encore car on n’a pas à gérer le z-index ou l’ordre des objets pour qu’ils se mettent bien dans l’image. Donc on crée sa scène, on rajoute des bidules, et voilà on a une planète qui tourne sur fond de voie lactée avec des tuyaux qui sortent et tout.
Ça me rappelle quand on s’amusait en VRML avec le plugin blaxxun :-)
Saying Goodbye to Firebug ★ Mozilla Hacks – the Web developer blog
▻https://hacks.mozilla.org/2017/10/saying-goodbye-to-firebug
The story of Firefox and Firebug is synonymous with the rise of the web.
So long Firebug, and thanx for all the fish :)
Intersection Observer comes to Firefox
▻https://hacks.mozilla.org/2017/08/intersection-observer-comes-to-firefox
Knowing whether or not an element is #visible has traditionally been difficult on the Web. Most solutions listen for scroll and resize events, then use #DOM #APIs like getBoundingClientRect() to manually calculate where elements are relative to the #viewport. This usually works, but it’s inefficient and doesn’t take into account other ways in which an element’s visibility can change, such as a large image finally loading higher up on the page, which pushes everything else downward.
These techniques kill performance, drain batteries, and would be completely unnecessary if the browser could just notify us whenever an element’s visibility changed.
At its most basic, the #IntersectionObserver API looks something like:
let observer = new IntersectionObserver(handler);
observer.observe(target); // <-- Element to watch
IntersectionObserver is available by default in Edge 15, Chrome 51, and Firefox 55, which is due for release next week.A polyfill is available which works effectively everywhere, albeit without the performance benefits of native implementations.
▻https://github.com/WICG/IntersectionObserver/tree/gh-pages/polyfill
Fathom: a framework for understanding web pages
▻https://hacks.mozilla.org/2017/04/fathom-a-framework-for-understanding-web-pages
#Readability, the basis of Safari and Firefox’s reader modes, is 1,800 lines of #JavaScript and was recently shut down. Chrome’s DOM Distiller is 23,000 lines of Java.But what if understanders were cheap to write? What if Readability could be implemented in just 4 simple rules?That scores within 7% of Readability’s output on a selection of its own test cases, measured by Levenshtein distance1. The framework enabling this is Fathom, and it drives the cost of writing understanders through the floor.Fathom is a mini-language for writing semantic extractors. The sets of rules that make up its programs are embedded in JavaScript, so you can use it client- or server-side as privacy dictates.
const rules = ruleset(
rule(dom('p,div,li,code,blockquote,pre,h1,h2,h3,h4,h5,h6'),
props(scoreByLength).type('paragraphish')),
rule(type('paragraphish'),
score(fnode => (1 - linkDensity(fnode,
fnode.noteFor('paragraphish')
.inlineLength))
* 1.5)),
rule(dom('p'),
score(4.5).type('paragraphish')),
rule(type('paragraphish')
.bestCluster({splittingDistance: 3,
differentDepthCost: 6.5,
differentTagCost: 2,
sameTagCost: 0.5,
strideCost: 0}),
out('content').allThrough(domSort))
); Fathom is a JavaScript framework for #extracting meaning from web pages, identifying parts like Previous/Next buttons, address forms, and the main textual content—or classifying a page as a whole. Essentially, it scores #DOM nodes and extracts them based on conditions you specify. A Prolog-inspired system of types and annotations expresses dependencies between scoring steps and keeps state under control. It also provides the freedom to extend existing sets of scoring rules without editing them directly, so multiple third-party refinements can be mixed together.
Firefox 52 est le premier navigateur à adopter les grilles CSS
▻https://www.macg.co/logiciels/2017/03/firefox-52-est-le-premier-navigateur-adopter-les-grilles-css-97683
