Re: New style for W3C Technical Report

It looks like the new style adds a new "overlarge" class to deal with 
this kind of situation; it may be a better choice:

>   *   - .overlarge for things that should be as wide as possible, even if
>   *     that overflows the body text area. This can be used on an item or
>   *     on its container, depending on the effect desired.
>   *     Note that this styling basically doesn't help at all when printing,
>   *     since A4 paper isn't much wider than the max-width here.
>   *     It's better to design things to fit into a narrower measure if possible.


/a

On 12/13/15 4:41 PM, Martin Thomson wrote:
> Hi Dom,
>
> The images in Section 5 of gUM are a little wide for the style, which
> causes the page to scroll horizontally.  Resampling those images to
> 800px should fix that.  I haven't noticed any other problems.
>
> On 11 December 2015 at 01:28, Dominique Hazael-Massieux <dom@w3.org> wrote:
>> Hi,
>>
>> W3C has set up a process through which the style of its Technical Reports
>> (and by extension, of editors drafts from its Working Groups) get revised on
>> a yearly basis.
>>
>> The first proposed revision was announced a few weeks ago:
>> https://lists.w3.org/Archives/Public/spec-prod/2015OctDec/0009.html
>>
>> To ensure the changes are viewed, reviewed and confirmed as acceptable for
>> our documents, I have updated the configuration of the editors drafts of
>> WebRTC 1.0 and Media Capture and Streams to use this new style:
>> http://w3c.github.io/webrtc-pc/webrtc.html
>> http://w3c.github.io/mediacapture-main/getusermedia.html
>>
>> While at this time this style is still "experimental", starting February
>> 2016 we should expect it to be the default for drafts published as WG
>> Technical Reports, and likely the default as well for editors drafts built
>> from ReSpec.
>>
>> Should you find bugs that look specific to our documents, please report them
>> here or on Github; if you find bugs that look generic with regard to the new
>> style, please follow the instructions in the mail linked from above. If
>> you're not sure, I'm happy to help determining which is which.
>>
>> I encourage the editors of other documents in the group to enable these new
>> styles as well so that they can either find bugs themselves or get readers
>> of the spec to do so. To make use of the new style, the ReSpec configuration
>> should be updated with "useExperimentalStyles: true".
>>
>> Dom
>>