summaryrefslogtreecommitdiff
path: root/test/test-pages/002
diff options
context:
space:
mode:
authorAndres Rey <[email protected]>2018-11-03 16:35:02 +0000
committerAndres Rey <[email protected]>2018-11-03 16:35:02 +0000
commit9e7ed7f7ade49317910076f041982a13eabab209 (patch)
tree4b5634797dcddaed6ff6baaa439a757704ba5517 /test/test-pages/002
parentde4334b8189b6697497194551f69ae26299a7a6c (diff)
Update test expectations
Diffstat (limited to 'test/test-pages/002')
-rw-r--r--test/test-pages/002/expected.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/test-pages/002/expected.html b/test/test-pages/002/expected.html
index e129084..8870180 100644
--- a/test/test-pages/002/expected.html
+++ b/test/test-pages/002/expected.html
@@ -1,4 +1,4 @@
-<div id="readability-page-1" class="page">
+
<div id="content-main">
<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 doesn’t play well with JavaScript’s recent focus on Promise- and generator-based asynchronous programming.</p>