- From: Takeshi Kurosawa via GitHub <sysbot+gh@w3.org>
- Date: Sun, 26 Jul 2020 03:07:58 +0000
- To: public-css-archive@w3.org
Thank you for your explanation and I feel like I'm not expressing myself correctly. I'm not against `scripting` media feature. Instead, I would like to use this for a few kinds of content. Replacing `scripting` with `update` is not my intention. > An opera-mini like product could definitely have initial-only scripts run on the server, then send the results to the device, with the device still having full capabilities for smooth scrolling and (declarative) animations / transitions. I misunderstood behaviors of Opera Mini. I understand why we can't drop `initial-only` though specifying `initial-only` precisely seems hard. > A user many have completely turned JS off, but their browser would still have full support for declarative animations / transitions. Yes, we can use `(update: fast) and (scripting: none)` for that. > e-ink viewers would generally fit into update:slow, but they could fall anywhere in terms of scripting. Yes, we can use `(update: slow) and (scripting: ...)` for that. -- GitHub Notification of comment by takenspc Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/503#issuecomment-663929785 using your GitHub account
Received on Sunday, 26 July 2020 03:07:59 UTC