01:41:56 RRSAgent has joined #restyle 01:41:56 logging to http://www.w3.org/2015/10/28-restyle-irc 01:42:07 .... [going through list of changes] 01:42:09 denis has changed the topic to: http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/ 01:42:52 ... [showing examples] 01:43:37 ... dl.switch 01:46:09 plinss has joined #restyle 01:46:21 Bert: I have a proposal for annoying-boxes 01:46:48 Fantasai: yes, mine needs improvement 01:46:52 -> https://drafts.csswg.org/css-box-3/ spec with pure-css warning-box using HTML4 only 01:47:07 Richard: I'd like to have the TOC higher 01:47:23 Fantasai: markup changes are out of scope 01:47:36 -> https://github.com/w3c/tr-design/pull/22 My PR for what r12a is mentioning 01:47:42 ... priority is on publication system 01:48:20 ... in 2016, I'd like to redo the entire spec templates 01:48:31 ... to take care of the above the fold issue 01:48:46 ... [show some possibilities] 01:49:27 http://fantasai.inkedblade.net/style/design/w3c-restyle/ 01:49:44 by robin and I, based on karl's post in spec-prod 01:50:08 ... it will take time to change the markup 01:50:41 ... we should make changes to the markup all at once, so we don't have to do it everyyear 01:50:59 ... it will be good to have people with design experience 01:51:09 s/everyyear/every year/ 01:51:25 ... a large set is using respec 01:51:27 karl has joined #restyle 01:51:31 ... few are using xmlspec 01:51:39 ... some are using bikeshed 01:51:50 RRSAgent, draft minutes 01:51:50 I have made the request to generate http://www.w3.org/2015/10/28-restyle-minutes.html karl 01:52:22 RRSAgent, make public 01:52:22 I'm logging. I don't understand 'make public', karl. Try /msg RRSAgent help 01:52:54 plh: webperf uses respec and doesn't care about the styling really 01:53:37 fantasai: do we want a side-by-side TOC? 01:53:56 ... rest is some cleaning and dealing with issues on github 01:54:33 ... [show demo of side TOC] 01:55:43 Tab: some issues on mobile, we need meta@viewport 01:56:07 plh: we might be able to convince the tooling and pubrules people 01:56:34 [folks are reporting issueson side TOC] 01:57:15 TabAtkins has joined #restyle 01:57:20 01:58:51 SteveZ has joined #restyle 01:58:55 (Can't browsers honor the PDF bookmarks properties and auto-generate a ToC, outside the viewport?) 01:59:08 Could, but won't. 01:59:52 http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/sample 02:00:04 Or rel=bookmark, then we can put the ToC in the 02:00:37 q+ 02:02:44 plh: at 1920, it would be nice to hide the toc if size is 50% or less 02:05:27 [talking about max-width on TR documents] 02:05:45 karlcow_ has joined #restyle 02:10:04 Bert2 has joined #restyle 02:11:36 Fantasai: couple of markup changes: meta viewport 02:12:27 ... and side-by-side section role=navigation (or something like that) 02:12:42 s/something like that/nav/ 02:12:49 ... and id=toc 02:13:39 ... plh should send a survey out about the questions 02:15:05 is there any plan regarding data extraction (microdata, rdfa, ...)? 02:18:17 ACTION: plh to publish the survey 02:19:08 denis, do you think changing the ID of the TOC, or wrapping it with a new element would affect Specberus/Echidna? 02:19:45 there's no check on the TOC itself so it won't be a problem 02:21:00 actually, the old pubrules does check the TOC id but that's very easy to update 02:21:44 [discussion on em, zoom, and tutti frutti] 02:23:42 q? 02:24:07 Richard: top page shouldn't be printed 02:24:27 ... and when the TOC disappears, jump to top of TOC instead of top page 02:24:29 fsasaki has joined #restyle 02:25:27 -> https://github.com/w3c/tr-design/pull/22 See my screenshots there for what r12a is saying 02:26:21 I have it here: https://github.com/w3c/tr-design/pull/22/files#diff-915dc9cf09496fd0b920c7d65dddd05cR68 02:26:41 q+ 02:32:09 q? 02:32:53 Zakim has joined #restyle 02:36:18 [various detailed tweaking discussions] 02:37:34 q+ 02:38:12 ack karl 02:38:21 Karl: problem on big tables 02:38:39 [can't be fixed without js. default is to put the table into a scrollbox] 02:39:05 Bert2: Where'd you put the hyphens in the words? 02:41:52 ScribeNick: Bert1 02:42:12 Discussion about the top-left status image 02:42:28 SimonSapin: Can be vector grapics? 02:42:41 Tab: sure, more efficient for bandwidth. 02:43:11 … also need to make it fixed to the ToC, i f the ToC has a background, otherwise it'll be invisible. 02:43:43 r12a: Notes don't seem to say that they are notes. 02:44:07 … unlike examples 02:45:04 … and the highlighted text doesn't look normative, due to the colored bar. 02:45:20 fantsai makes new sample. Reload! 02:47:04 RRSAgent, draft minutes 02:47:04 I have made the request to generate http://www.w3.org/2015/10/28-restyle-minutes.html denis 02:48:15 liam: I like things aligned, so would be nice to have the logo aligned with the top of the ToC [in wide view] 02:49:03 fantasai: I'd like to redesign the whole top, for a next redesign 02:49:56 liam: Can we have 1 or 2 sentences at the start to explain what a spec is? 02:50:28 Proposal for an alternative W3C logo: http://i.imgur.com/f5bogpL.jpg 02:50:43 fantasai: Next year want to do a compact top with links to notes about status. 02:50:59 karlcow_: Want me to make a more mobile-friendly version of that. 02:51:18 fantasai: So far only a demo, Need proper design first. 02:51:40 s/that./that?/ 02:52:28 plh: Process calls for final design by 30 Oct. Only tweaks afterwards. 02:53:21 fantasai: Removing the side ToC will be easy, just remove some CSS rules. Integrating comments may take more time. 02:54:00 plh: I'll need to start writing the e-mail soon. I'd need a stable snapshot that won't chnage after Oct 31 02:54:24 fantasai: I think people should see the latest, with their comments integrated. 02:55:01 fantasai: Not yet done much on inline styles for code and WebIDL. 02:55:17 http://www.w3.org/International/docs/styleguide 02:55:34 http://www.w3.org/International/docs/styleguide#inline 02:55:42 s/inline styles for code/styles for inline code/ 02:56:15 r12a: Extra whitespace between headings as you did is great. I vote in favor. 02:56:26 +1 to extra spacing too 02:57:04 fantasai: CSS style had even more, but I got comments and reduced the space bit. 02:57:09 https://www.w3.org/2002/09/wbs/1/tr_toc_2016/ 02:57:31 plh: Questionnaire [see url]. Any feedback? 02:58:33 where the window is sufficiently wide (i.e. the maximum line length required by a11y is satisfied and extra space is currently going to margins) 02:58:47 s/required/recommended/ 03:00:37 fantasai: I need to check question 3: the exact mark-up may be different from