weflow-cli 1.8.1 → 1.8.2
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/CHANGELOG.md +17 -0
- package/package.json +1 -1
- package/resources/panel/panel.css +12 -3
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,23 @@ The npm package is published separately from GitHub. It may lag behind the `mast
|
|
|
4
4
|
|
|
5
5
|
All notable user-facing changes are recorded here. This project follows [Semantic Versioning](https://semver.org/).
|
|
6
6
|
|
|
7
|
+
## 1.8.2
|
|
8
|
+
|
|
9
|
+
### Changed
|
|
10
|
+
|
|
11
|
+
- **The ball no longer casts a drop shadow.** The user reported that the mascot's background was
|
|
12
|
+
"not fully transparent" and asked for another round of matting. **It was not the image**: the PNGs
|
|
13
|
+
are clean - all four corners are `(0,0,0,0)`, the solid areas sit at alpha 253/255, and the only
|
|
14
|
+
low-alpha pixels are 674 anti-aliasing edge pixels within 4-8 px of solid ones. What they were
|
|
15
|
+
seeing was `filter: drop-shadow(...)` on the ball, which was there deliberately ("a transparent
|
|
16
|
+
subject needs it to separate from a light wallpaper") and pinned by a test.
|
|
17
|
+
|
|
18
|
+
The trade-off is recorded rather than glossed: that earlier check covered whether the **transparent
|
|
19
|
+
background** stayed legible against light, mid and dark wallpapers - not whether it does so
|
|
20
|
+
**without a shadow**, so this is a new, unverified visual change. If the cat ends up looking
|
|
21
|
+
unmoored, the line to bring back is a much fainter one, and it is written in `panel.css` next to
|
|
22
|
+
the `filter: none`. Hover feedback survives on `scale(1.02)` and `brightness(1.08)`.
|
|
23
|
+
|
|
7
24
|
## 1.8.1
|
|
8
25
|
|
|
9
26
|
### Changed
|
package/package.json
CHANGED
|
@@ -129,8 +129,17 @@ header {
|
|
|
129
129
|
那是因为它的内容本来只占 59%x67%——**余量是结果,不是规则**。) */
|
|
130
130
|
background-color: transparent;
|
|
131
131
|
|
|
132
|
-
/*
|
|
133
|
-
|
|
132
|
+
/* **不画投影**(2026-09-29 用户要求去掉的)。
|
|
133
|
+
它原先在这里,理由是"透明主体靠它跟浅色壁纸分开";用户看到的是**猫轮廓外一圈灰黑影**,
|
|
134
|
+
读成了"背景没完全透明"。**先澄清一件事:那不是图的问题** —— 实测这几张 PNG 的四角是
|
|
135
|
+
`(0,0,0,0)`,实心区 alpha 253/255,低 alpha 像素只有 674 个且都贴着实心区 4-8 像素
|
|
136
|
+
(是描边锯齿,不是底)。所以问题在这一行 CSS,不在抠图。
|
|
137
|
+
代价要知道:去掉之后深色猫在某些壁纸上的分离感会弱一点。当初试过浅/中/深三种底,
|
|
138
|
+
但那回测的是"**透明底**读不读得清",不是"**没有投影**读不读得清" —— 所以这条是新的、
|
|
139
|
+
还没验过的视觉变化。真觉得飘的话,把它改回一行很淡的就够:
|
|
140
|
+
`filter: drop-shadow(0 2px 4px rgba(0, 0, 0, .22));`
|
|
141
|
+
悬停时仍然看得出反馈:`transform: scale(1.02)` 与 `brightness(1.08)` 都还在。 */
|
|
142
|
+
filter: none;
|
|
134
143
|
/* 回弹曲线(不是 ease):松手时从压扁弹回原状会**轻微过冲**一下,那就是"弹"的感觉。
|
|
135
144
|
窗口就是球这么大,过冲出来的那点边缘靠出图时留的 2% 余量兜住。 */
|
|
136
145
|
transition: transform .16s cubic-bezier(.34, 1.56, .64, 1), filter .16s ease;
|
|
@@ -257,7 +266,7 @@ body.quota #ball .glow { animation: none; opacity: .85; }
|
|
|
257
266
|
/* 悬停:微微放大 + 阴影加深 + 提亮 —— 三样一起才够"这里能点"。
|
|
258
267
|
**放大只敢到 1.02**:出图按"实心像素最远点 ≤ 0.98 × 半径"缩放(见 `.face` 那段),
|
|
259
268
|
1.02 倍时圆外只剩 1 个像素(实测),再大就开始削掉猫的外缘。 */
|
|
260
|
-
#ball:hover { transform: scale(1.02); filter:
|
|
269
|
+
#ball:hover { transform: scale(1.02); filter: brightness(1.08); }
|
|
261
270
|
/* 按下:压扁。**只往小里做** —— 放大或位移会把内容顶出窗口、被窗口边裁掉。 */
|
|
262
271
|
#ball:active { transform: scale(.92); }
|
|
263
272
|
|