Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[mediaqueries][mediaqueries-5] should 'initial-only' have an explicit minimum threshold? #503

Open
tantek opened this issue Sep 20, 2016 · 4 comments
Open

[mediaqueries][mediaqueries-5] should 'initial-only' have an explicit minimum threshold? #503

tantek opened this issue Sep 20, 2016 · 4 comments
Assignees
@frivoal
Labels
mediaqueries-5

Comments

@tantek
Copy link
Member

tantek commented Sep 20, 2016 •
edited by frivoal
Loading

https://drafts.csswg.org/mediaqueries-5/#scripting

Formerly "Issue 4" inline in the spec, brought here to capture and discuss:

"
Should there be an explicit minimum threshold to meet before a UA is allowed to claim initial-only? Having one would mean authors would know what they can depend on, and could tailor their scripts accordingly. On the other hand, pinpointing that threshold is difficult: if it is set too low, the scripting facilities that authors can depend on may be to constrained to be practical, even though actual UAs may potentially all support significantly more. But trying to set it higher may cause us to exclude UAs that do support scripting at loading time, but restrict it in some cases based on complex heuristics. For instance, conservative definitions likely include at least running all inline scripts and firing the DOMContentLoaded event. But it does not seem useful for authors to constrain themselves to this if most (or maybe all) initial-only UAs also load external scripts (including async and defer) and fire the load event. On the other hand, requiring external scripts to be loaded and the load event to be fired could exclude UAs like Opera mini, which typically do run them, but may decide not to based on timeouts and other heuristics.
"

Feel free to adjust issue name/title and "[...]" labels according to where this feature ends up. Thanks!
@dbaron dbaron added the mediaqueries-4 Current Work label Sep 28, 2016
@frivoal frivoal self-assigned this May 5, 2017
@frivoal frivoal added mediaqueries-5 and removed mediaqueries-4 Current Work labels May 5, 2017
@frivoal frivoal changed the title [mediaqueries][mediaqueries-4][mediaqueries-5] should 'initial-only' have an explicit minimum threshold? [mediaqueries][mediaqueries-5] should 'initial-only' have an explicit minimum threshold? Jun 15, 2017
@takenspc
Copy link

I believe (scripting: initial-only) overlaps update media feature and latter one is more generic as typical printed pages don't support both CSS and JavaScript updates (transitions, animations and so on). UAs like Opera Mini update pages in some conditions so that (update: slow) can be used.

So, I propose that

  • drop initial-only from scripting media feature
  • suggest using (update: none) for printed pages
  • suggest using (update: slow) for UAs like Opera Mini

Though I believe that update media feature covers (scripting: initial-only) uses cases, please let me know if I missed something.

@frivoal
Copy link
Collaborator

frivoal commented Jul 24, 2020

Hmmm. update and script seem somewhat correlated, but I don't think the relationship is strong enough to have one fully replace the other:

  • 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.

  • A user many have completely turned JS off, but their browser would still have full support for declarative animations / transitions.

  • e-ink viewers would generally fit into update:slow, but they could fall anywhere in terms of scripting.

@takenspc
Copy link

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.

@frivoal
Copy link
Collaborator

frivoal commented Jul 28, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@frivoal frivoal

Labels
mediaqueries-5
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tantek @frivoal @dbaron @takenspc