<table class="standard-table" summary="This table details what tea we liked to drink back in the heady month of December 2015"> +<table class="standard-table"> <caption>Favorite teas, December 2015</caption> <thead> <tr> diff --git a/files/en-us/mozilla/firefox/releases/87/index.html b/files/en-us/mozilla/firefox/releases/87/index.html index 1deaf65e192aeb6..9f1025e2fd6ca99 100644 --- a/files/en-us/mozilla/firefox/releases/87/index.html +++ b/files/en-us/mozilla/firefox/releases/87/index.html @@ -55,7 +55,7 @@HTTP
network.cors_preflight.allow_client_cert preference ({{bug(1511151)}}).strict-origin-when-cross-origin (from no-referrer-when-downgrade), reducing the risk of leaking referrer information in cross-origin requests ({{bug(1589074)}}).Referrer-Policy has been changed to strict-origin-when-cross-origin (from no-referrer-when-downgrade), reducing the risk of leaking referrer information in cross-origin requests ({{bug(1589074)}}).Content-Length has been added to the list of CORS-safelisted response headers ({{bug(1460299)}}).This example demonstrates how to add an addEventListener() that can be aborted with an {{domxref("AbortSignal")}}.
<table id="outside"> <tr><td id="t1">one</td></tr> @@ -263,7 +263,7 @@-HTML
</table>
// Add an abortable event listener to table const controller = new AbortController(); @@ -285,7 +285,7 @@JavaScript
In the above example just above, we modify the code in the previous example such that after the second row’s content changes to "three", we call
-abort()from the {{domxref("AbortController")}} we passed to theaddEventListener()call. That results in the value remaining as "three" forever — because we no longer have any code listening for a click event.Result
+Result
{{EmbedLiveSample('add_a_abortable_listener')}}
diff --git a/files/en-us/web/api/fetch_api/using_fetch/index.html b/files/en-us/web/api/fetch_api/using_fetch/index.html index 3fdbfb97ed697c7..0902c5d69329679 100644 --- a/files/en-us/web/api/fetch_api/using_fetch/index.html +++ b/files/en-us/web/api/fetch_api/using_fetch/index.html @@ -25,7 +25,7 @@
fetch() won’t reject on HTTP error status even if the response is an HTTP 404 or 500. Instead, it will resolve normally (with ok status set to false), and it will only reject on network failure or if anything prevented the request from completing.fetch() won’t send cross-origin cookies unless you set the credentials init option. (Since April 2018. The spec changed the default credentials policy to same-origin. Firefox changed since 61.0b13.)fetch() won’t send cross-origin cookies unless you set the credentials init option. (Since April 2018. The spec changed the default credentials policy to same-origin. Firefox changed since 61.0b13.)A basic fetch request is really simple to set up. Have a look at the following code:
diff --git a/files/en-us/web/html/element/hgroup/index.html b/files/en-us/web/html/element/hgroup/index.html index 609544746af2185..6421727870fbaf2 100644 --- a/files/en-us/web/html/element/hgroup/index.html +++ b/files/en-us/web/html/element/hgroup/index.html @@ -132,7 +132,7 @@The presence of hgroup may remove information reported to assistive technology about the subheading portion of the heading group.
| Pro(s) | @@ -412,8 +412,8 @@
|---|
// Technique 1 @@ -450,7 +450,7 @@-#2: {{jsxref("Object.create")}}
var inst = new bar; console.log(inst.foo_prop); console.log(inst.bar_prop)
| Con(s) | Not supported in IE8 and below. However, as Microsoft has discontinued extended support for systems running IE8 and below, that should not be a concern for most applications. Additionally, the slow object initialization can be a performance black hole if using the second argument, because each object-descriptor property has its own separate descriptor object. When dealing with hundreds of thousands of object descriptors in the form of objects, that lag time might become a serious issue. |
|---|
// Technique 1 @@ -498,7 +498,7 @@-#3: {{jsxref("Object.setPrototypeOf")}}
var inst = new bar; console.log(inst.foo_prop); console.log(inst.bar_prop)
| Con(s) | Ill-performing. Should be deprecated. Many browsers optimize the prototype and try to guess the location of the method in memory when calling an instance in advance; but setting the prototype dynamically disrupts all those optimizations. It might cause some browsers to recompile your code for de-optimization, to make it work according to the specs. Not supported in IE8 and below. |
|---|
// Technique 1 @@ -541,7 +541,7 @@-#4: Setting the {{jsxref("Object/proto","__proto__")}} prope }; console.log(inst.foo_prop); console.log(inst.bar_prop)