« Adding alpha channels or chroma keys to JPEG images | Main | Good News about VP8 Licensing »

Open Web Platform Weekly Summary - 2013-03-04 - 2013-03-10

This is our weekly Openweb Platform Summary from March 4, 2013 to March 10, 2013. You can read again the last week blog post. Your comments are helpful.

[CSS] Printed Pages Margins

When printing a Web page, the browser is often adding margins and sometimes meta-information. Users can deactivate this manually, but what if the Web page could control this state. It's what Julian Viereck is proposing. A discussion followed on the right way to do this and if it was a good idea.

[CSS] Display Box, A Separate Property.

The CSS Display Module is currently a proposal by Tab Atkins and a few others to redefine the way the display property is working. At this time, it is not yet approved by the CSS WG. They are advocating a complete separate property for display and not a longhand property. It is common for CSS to have these constructs short/longhand. For example, think about border and border-bottom. Tab is exposing some of the issues with the value none. The thread is about the suggestion.

[CSS] Overflow Inside Multicolumn Elements

There was a call recently for use cases on overflow when the layout has multicolumns. The current behavior in WebKit is slightly different from the other browsers. See the full discussion.

Web Components, The First Editor Draft

Finally, the first editor's draft of Web components has been published. As the abstract says: Web Components are a way to include and reuse HTML documents in other HTML documents. The Web components are enabled through a new link type and a link element. For example,

<link rel="component" href="/components/heart.html">

Note that the value is not stable yet. And it might change in the future. See the initial discussions about it.

Life of W3C

Filed by Karl Dubost on March 10, 2013 3:11 PM in CSS, Open Web, Web Applications
| | Comments (1) | TrackBacks (0)

Comments

Caitlin # 2013-03-19

rel value for "component" could probably be "subdocument". That's nice and accurate.

Leave a comment

Note: this blog is intended to foster polite on-topic discussions. Comments failing these requirements and spam will not get published. Please, enter your real name and email address. Every individual comment is reviewed by the W3C staff. This may take some time, thank you for your patience.

You can use the following HTML markup (a href, b, i, br/, p, strong, em, ul, ol, li, blockquote, pre) and/or Markdown syntax.

Your comment


About you

This blog is written by W3C staff and working group participants,
 and maintained by Coralie Mercier.
Authorized parties may log in to create a new entry.
Powered by Movable Type, magpierss and a lot of Web Technology