edf2csv 0.6.75 → 0.6.77
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/CHANGELOG.md +33 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,39 @@
|
|
|
3
3
|
Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
|
|
4
4
|
major version is 0, a minor bump may contain breaking changes.
|
|
5
5
|
|
|
6
|
+
## 0.6.77
|
|
7
|
+
|
|
8
|
+
### the skip link could be focused and stay off-screen
|
|
9
|
+
|
|
10
|
+
The skip link added in 0.6.66 revealed itself on `:focus-visible`, which is the right selector for
|
|
11
|
+
a control that can also be clicked and the wrong one here. A skip link is the first element in the
|
|
12
|
+
document and sits off-screen until focused, so there is no pointer path to it: everything that
|
|
13
|
+
ever focuses it is a keyboard or an assistive technology, and there is no mouse-focus ring to
|
|
14
|
+
suppress. What `:focus-visible` adds in that situation is a heuristic that can decline — focus
|
|
15
|
+
moved by a script, or a browser whose rules differ — and when it declines the link is focused and
|
|
16
|
+
still off-screen, which is worse than having no skip link at all, because the reader's focus is
|
|
17
|
+
now somewhere they cannot see.
|
|
18
|
+
|
|
19
|
+
`:focus` has no such gap. The built stylesheet was checked for the rule and the link confirmed as
|
|
20
|
+
the document's active element after focus; the visual reveal cannot be exercised in a window that
|
|
21
|
+
does not itself have focus, which is the only part of this a browser in the background will not
|
|
22
|
+
show you.
|
|
23
|
+
|
|
24
|
+
## 0.6.76
|
|
25
|
+
|
|
26
|
+
### the homepage guard would have passed a homepage with no heading
|
|
27
|
+
|
|
28
|
+
0.6.62 made the build fail if the homepage server-rendered to fewer than 150 words, which catches
|
|
29
|
+
a render that collapsed to nothing and nothing else. It would pass a homepage that lost its h1,
|
|
30
|
+
or whose lede fell back to placeholder text, or that rendered four of its five sections — every
|
|
31
|
+
one of them the failure the step exists to prevent, stopping just short of total. The count was
|
|
32
|
+
never the claim being made; it was the easiest thing to measure.
|
|
33
|
+
|
|
34
|
+
The build now asserts the four things a crawler is read for: a heading, the sentence that says
|
|
35
|
+
what the tool does, the install command, and a link into the documentation. Deleting the lede
|
|
36
|
+
fails the build with the name of what went missing, which is how it was checked before being
|
|
37
|
+
committed.
|
|
38
|
+
|
|
6
39
|
## 0.6.75
|
|
7
40
|
|
|
8
41
|
### the sitemap dated the homepage from files the homepage is not written in
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.77",
|
|
4
4
|
"description": "Convert EDF, EDF+ and BDF biosignal recordings (European Data Format) to CSV from the command line. Local, streaming, and never resamples or alters units.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"edf",
|