https://eslint.org/docs/rules/use-isnan

This is a proposal to modify the use-isnan rule.

Current rule setting:

use-isnan: "error"

Proposed rule setting:

["error", {"enforceForSwitchCase": true}]

The switch statement internally uses the === comparison to match the expression's value to a case clause.
Therefore, it can never match _case NaN. Also, `swit

Hi,

The results computed here could be difficult to read and their is no documentation about how they are computed.

The idea is to display :

• CPU / RAM of sieger
• CPU / RAM of targets
• Runtime / flag compilation
• Steps (warm-up ...)
• Sieger tool
• Sieger options

Results,

Supersed #68

Issue

In v7.1.0:

When you declare a custom file in bumpFiles standard-version will no longer update normal package.json, composer.json, lockfiles, etc. declared in the defaults.

This is fine (I don't think this is a bug because maybe you don't want it to bother with the defaults), but I think it should be mentioned in the documentation that when you do declare bumpFiles in your c

Some people seem to read https://html.spec.whatwg.org/multipage/forms.html#dom-form-nameditem as implying that a new nodelist should be returned each time when there are multiple matching elements. That's not the intent, I assume, and it might be worth clarifying the spec to make it clear.

All browsers I tested (Firefox, Chrome, Safari) return the same nodelist on multiple accesses.

There should be a linter, after the spec in the main readme is filled out. The linter will most likely use remark and remark-lint. This is the planning issue for the linter. Please subscribe here, and open new issues for tangential questions about Standard Readme.

https://aomediacodec.github.io/av1-avif/#avif-mime-definition

.avif image/avif
.avifs image/avif-sequence

This is being prototyped in Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=960620

Checklist

Please ensure the following tasks are completed before filing a bug report.

• Read and understood the [Code of Conduct][code-of-conduct].
• Searched for existing issues and pull requests.

Description

Description of the issue.

The following code produces an array whose shape does not match what I'd expect:

It looks like conventional commits do not explicitly specify whether a description should begin with an uppercase or lowercase letter, although all the examples appear to begin with a lowercase letter.

Could the next revision recommend that the description starts with a lowercase letter? Something like:

A description SHOULD begin with a lowercase letter, except when the first word would no

What version of this package are you using?
"eslint-config-standard": "^14.1.0"

What operating system, Node.js, and npm version?
node.js is 10.18.0 and npm version is 6.13.4

What happened?
when i use this npm with eslint, it get something wrong to notice me the errors in the javascript file of my project.like this error:
1:1 error Definition for rule 'no-async-promise-ex

Members that are conditionally present are hard to work with. We should just make it take several 3 string enum values or a URL and convert null and failure to 2 of those string enum values as we get a result from the header parser (the third value being the default).

1. I don't think this WebSocket example would work as expected. The onclose event handler is set by both the source and the sink which obviously can't work.

2. I'm confused on why the onclose event handler is set to null for the WebSocketSink. For what purpose is this being done?

this._ws.onclose = () => controller.error(new Err

https://dom.spec.whatwg.org/#dom-element-attachshadow
Item 2 in the list says:

If context object’s local name is not a valid custom element name, "article", "aside", "blockquote", "body", "div", "footer", "h1", "h2", "h3", "h4", "h5", "h6", "header", "main" "nav", "p", "section", or "span", then throw a "NotSupportedError" DOMException.

The above sentence is ambiguous. The enumeration ca

README states:

Why not use WebAssembly?

There are massive existing untyped codebases, and there is no easy way to convert an untyped, garbage collected language to WebAssembly. And even if there were, there is no guarantee that it would be any faster to transmit/parse/start than what we currently have.

whereas WebAssembly FAQ states:

The kind of binary format being considered f

The controls are worded in a few different ways right now.

Most of them are affirmative:

No sensitive data is written to application logs.

But some are conditional:

The app’s local storage should be wiped after an excessive number of failed authentication attempts.

I propose to rewrite the second type to the first type:

The app’s local storage is wiped after an excessive nu

In chapter 17. Screen capture, section 17.2 Take Element Screenshot:

The Take Element Screenshot command takes a screenshot of the visible region encompassed by the bounding rectangle of an element.

"bounding rectangle" links

Introduction

This is a proposal for adding more explicit and extensive, and even ASCII art inspired support for set algebra in openCypher.

In my opinion sets of graphs is a once-in-a-lifetime opportunity that is much more than a revival: Doing set algebra on sets of graphs is potentially several orders of magnitude more powerful than SQL-based set algebra (or the simple lists etc. offered

See firsttimersonly.com.

This could serve as a good forcing function towards improving our contribution guidelines, documentation, and making our community more welcoming to newbies.

As an occasional standards-user, the lack of a succinct expression of the grammar for valid URL strings is rather frustrating. It makes it rather difficult to follow what's going on and, in particular, to work out whether a given thing is a valid URL. A grammar in EBNF or a similar form would be greatly appreciated and make this spec significantly easier to understand.

The class comment of MonetaryAmountFormat has two code snippets. Both of them are full of compile errors

MonetaryAmountFormat f = MonetaryFormats.getInstance(loc);
f.setStyle(f.getStyle().toBuilder().setPattern("###.##;(###.##)").build());

• there are no #setStyle and #getStyle methods
• there is no #getInstance method on MonetaryFormats, you probably mean `#getAmount

Context: whatwg/html#3195
Context: whatwg/xhr#202

FormData should have ability to add an entry for a submitter button when it appends entries for a <form>.

We have multiple options of how to specify submitter. See five comments since whatwg/html#3195 (comment)

A) `constructor(optional (

Can you add all the labels to this issue to show what they look like with the configured colors?