Merge pull request #22 from gijsk/fix-empty-classes

Don't create/leave empty class attributes around all the nodes we're using. r=margaret
pull/24/head
Margaret Leibovic 9 years ago
commit 03d9e36161

@ -668,7 +668,7 @@ Readability.prototype = {
// To ensure a node does not interfere with readability styles,
// remove its classnames.
siblingNode.className = "";
siblingNode.removeAttribute("class");
// Append sibling and subtract from our list because it removes
// the node when you append to another node.

@ -1,4 +1,4 @@
<div id="readability-page-1" class="page"><section class="">
<div id="readability-page-1" class="page"><section>
<p><strong>So finally you're <a href="file:///code/2013/testing-frontend-javascript-code-using-mocha-chai-and-sinon/">testing your frontend JavaScript code</a>? Great! The more you
write tests, the more confident you are with your code… but how much precisely?
That's where <a href="http://en.wikipedia.org/wiki/Code_coverage">code coverage</a> might

@ -1,4 +1,4 @@
<div id="readability-page-1" class="page"><article class="" role="article">
<div id="readability-page-1" class="page"><article role="article">
<p>For more than a decade the Web has used XMLHttpRequest (XHR) to achieve asynchronous requests in JavaScript. While very useful, XHR is not a very nice API. It suffers from lack of separation of concerns. The input, output and state are all managed by interacting with one object, and state is tracked using events. Also, the event-based model doesnt play well with JavaScripts recent focus on Promise- and generator-based asynchronous programming.</p>
<p>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API">Fetch API</a> intends to fix most of these problems. It does this by introducing the same primitives to JS that are used in the HTTP protocol. In addition, it introduces a utility function <code>fetch()</code> that succinctly captures the intention of retrieving a resource from the network.</p>
<p>The <a href="https://fetch.spec.whatwg.org">Fetch specification</a>, which defines the API, nails down the semantics of a user agent fetching a resource. This, combined with ServiceWorkers, is an attempt to:</p>

@ -1,6 +1,6 @@
<div id="readability-page-1"
class="page">
<p id="first" class="">Regarding item# 11111, under sufficiently extreme conditions, quarks may
<p id="first">Regarding item# 11111, under sufficiently extreme conditions, quarks may
become deconfined and exist as free particles. In the course of asymptotic
freedom, the strong interaction becomes weaker at higher temperatures.
Eventually, color confinement would be lost and an extremely hot plasma
@ -8,7 +8,7 @@ class="page">
of matter is called quark-gluon plasma.[81] The exact conditions needed
to give rise to this state are unknown and have been the subject of a great
deal of speculation and experimentation.</p>
<p id="second" class="">Regarding item# 22222, under sufficiently extreme conditions, quarks may
<p id="second">Regarding item# 22222, under sufficiently extreme conditions, quarks may
become deconfined and exist as free particles. In the course of asymptotic
freedom, the strong interaction becomes weaker at higher temperatures.
Eventually, color confinement would be lost and an extremely hot plasma
@ -16,7 +16,7 @@ class="page">
of matter is called quark-gluon plasma.[81] The exact conditions needed
to give rise to this state are unknown and have been the subject of a great
deal of speculation and experimentation.</p>
<p id="third" class="">Regarding item# 33333, under sufficiently extreme conditions, quarks may
<p id="third">Regarding item# 33333, under sufficiently extreme conditions, quarks may
become deconfined and exist as free particles. In the course of asymptotic
freedom, the strong interaction becomes weaker at higher temperatures.
Eventually, color confinement would be lost and an extremely hot plasma

Loading…
Cancel
Save