|
5 posts total
 A post about some of the ways I try to meet the needs of a browser DevRel team that need to share information about new things, with those of developers who need to know what actually works now. If you write or speak about the web, perhaps some of these ideas will help you too. For years, I've been hoping for more of the paged media specifications to come to browsers. In the next version of Chrome (131, now in beta) the ability to create your own header and footer content for printed content is here! Find out more in this post.  @rachelandrew Thank you for the useful post. I'm looking forward to know more about the overflow handling of margin boxes and the print media styles cascade relations.  @rachelandrew I love & sympathise with the tip about using the bug tracker in the article. Open source lyfe.
Show previous comments
I recorded a short video for TPAC to introduce the reading-flow property, which now has an experimental implementation in Chrome. https://www.w3.org/2024/09/TPAC/demo-css.html There's also bonus Max in this video. I think he may be the distracting background I was warned about. He had been asleep in his hammock, which is just out of shot, and quietly emerged. Watch for the CSS, or the cat, or both! |
Gregory's Server
@rachelandrew thank you for writing this Rachel. Totally agree.
I’ve been guilty of this several times myself. Though on the Edge blog we try to restrict ourselves to stable features only (though sometimes features that are chromium only).
My work on web-features and Baseline helped me gain new perspectives on this.