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.

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

Hole in CSS rendering model: initial and transitional page paints #3688

Open
tantek opened this Issue Feb 28, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@tantek
Copy link
Contributor

tantek commented Feb 28, 2019

Browsers currently paint a window with a default background before/while loading web pages, CSS, and other resources. This happens both upon opening a new window with a URL (initial paint), and when navigating from one page to another (transitional paint), and is currently unspecified by the CSS rendering model.

This hole in the CSS rendering model results in proposals to use meta tags instead, such as viewport, and potentially for a dark mode.

I pointed this out in the discussion on Issue 3299 in the afternoon of 2019-02-26 at the CSSWG meeting.

Rather than awkwardly punting this area of rendering behavior(s) to an HTML meta tag or other non-CSS solution, CSS should define how browsers should (or at least may) render initial and transitional paints, preferably with a feature that permits author control, especially (at least) between pages of the same origin.

Prior related work:

Anything specified in the CSS rendering model for handling initial and transitional page paints should reference the HTML specification and hook into the DOM and states described in: HTML Standard: 7.7 Session history and navigation.

Labels: Needs Thought, unknown/future spec

(Originally published at: http://tantek.com/2019/058/b1/hole-css-initial-transitional-page-paints)

@adactio

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.