Re: Fixing the TOC issues

:( It is PhistucK (or Phistuck, or Phis, or nothing at all), not Phil.

As long as toggling it off widens the form again, it sounds fine.


☆*PhistucK*


On Fri, Jun 7, 2013 at 8:02 PM, Doug Schepers <schepers@w3.org> wrote:

> Hi, Leanne, Phil-
>
> We talked about making the TOC togglable... maybe that would help, in
> addition to other more automated solutions?
>
> Regards-
> -Doug
>
>
> On 6/7/13 12:38 PM, Lea Verou wrote:
>
>> Honestly, I don‘t know. I'll need to look into it, but in general MW
>> makes it pretty difficult to do things like this. Worst case, we could
>> check the URL and add a class with JS.
>>
>> Lea Verou
>> W3C developer relations
>> http://w3.org/people/all#leahttp://lea.verou.me ✿ @leaverou
>>
>>
>>
>>
>>
>>
>> On Jun 7, 2013, at 14:06, PhistucK <phistuck@gmail.com
>> <mailto:phistuck@gmail.com>> wrote:
>>
>>  Apology accepted.
>>>
>>> Perhaps move it beyond the content area, to the sides, in wide screens
>>> (1280 and up)?
>>> I guess the current approach makes sense in content pages, but less so
>>> in editing pages and we could lower the threshold of "wider" there to
>>> 1280.
>>> Is it possible to separate this logic for content and editing pages?
>>>
>>>
>>> ☆*PhistucK*
>>>
>>>
>>>
>>> On Fri, Jun 7, 2013 at 7:31 PM, Lea Verou <lea@w3.org
>>> <mailto:lea@w3.org>> wrote:
>>>
>>>     Apologies about the name, I read it wrong. I thought t was Phil +
>>>     a last name. Didn't mean to insult you.
>>>
>>>     Regarding the TOC, perhaps we could only show it for wider
>>>     screens. Thoughts, everyone?
>>>
>>>     Lea Verou
>>>     W3C developer relations
>>>     http://w3.org/people/all#leahttp://lea.verou.me
>>>     <http://lea.verou.me/> ✿ @leaverou
>>>
>>>
>>>
>>>
>>>
>>>
>>>     On Jun 7, 2013 <tel:2013>, at 13:51, PhistucK <phistuck@gmail.com
>>>     <mailto:phistuck@gmail.com>> wrote:
>>>
>>>      PhistucK (or Phistuck, or Phis, or nothing at all), not Phil.
>>>>     This is the second time already, which makes this rather insulting.
>>>>
>>>>     The issue is that it narrows the area of the form.
>>>>     Note that I have a somewhat wide screen (1280x800), so I get
>>>>     redundant side spacing as well as a narrow form.
>>>>
>>>>
>>>>     ☆*PhistucK*
>>>>
>>>>
>>>>     On Fri, Jun 7, 2013 <tel:2013> at 7:12 PM, Lea Verou <lea@w3.org
>>>>
>>>>     <mailto:lea@w3.org>> wrote:
>>>>
>>>>         Hi Phil,
>>>>
>>>>         Is that an issue? I edited a page today and I found it very
>>>>         helpful.
>>>>
>>>>         Cheers,
>>>>         Lea
>>>>
>>>>         Lea Verou
>>>>         W3C developer relations
>>>>         http://w3.org/people/all#leahttp://lea.verou.me
>>>>         <http://lea.verou.me/> ✿ @leaverou
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>         On Jun 7, 2013 <tel:2013>, at 13:27, PhistucK
>>>>         <phistuck@gmail.com <mailto:phistuck@gmail.com>> wrote:
>>>>
>>>>          Can the table of content be removed when editing pages?
>>>>>         http://docs.webplatform.org/w/**index.php?title=dom/methods/**
>>>>> hasAttributeNS&action=formedit<http://docs.webplatform.org/w/index.php?title=dom/methods/hasAttributeNS&action=formedit>
>>>>>         It shows up for me there.
>>>>>
>>>>>         Thank you!
>>>>>
>>>>>
>>>>>         ☆*PhistucK*
>>>>>
>>>>>
>>>>>         On Sat, May 25, 2013 <tel:2013> at 3:42 AM, Lea Verou
>>>>>
>>>>>         <lea@w3.org <mailto:lea@w3.org>> wrote:
>>>>>
>>>>>             Hi all,
>>>>>
>>>>>             Thanks for the feedback both in the list and in today’s
>>>>>             call.
>>>>>             I fixed the issues (hopefully!) and also added media
>>>>>             queries to make it adapt to smaller screens. So
>>>>>             currently it's outside the page for resolutions with >
>>>>>             1400px width, inside the content area for resolutions
>>>>>             between 700px and 1400px and a section at the top for
>>>>>             resolutions below 700px. Furthermore, between 500px and
>>>>>             700px it’s two column, whereas below 500px it’s a single
>>>>>             column list.
>>>>>             I deployed in current too, so it’s live now.
>>>>>
>>>>>             Hope you like it.
>>>>>
>>>>>             Cheers,
>>>>>             Lea
>>>>>
>>>>>             Lea Verou
>>>>>             W3C developer relations
>>>>>             http://w3.org/people/all#leahttp://lea.verou.me
>>>>>             <http://lea.verou.me/> ✿ @leaverou
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>             On May 24, 2013 <tel:2013>, at 19:20, Mike Sierra
>>>>>             <letmespellitoutforyou@gmail.**com<letmespellitoutforyou@gmail.com>
>>>>>             <mailto:letmespellitoutforyou@**gmail.com<letmespellitoutforyou@gmail.com>>>
>>>>> wrote:
>>>>>
>>>>>              I like it a lot better floating outside the content.
>>>>>>              The animation seems jerky, which is odd considering it
>>>>>>             uses CSS transitions.  Are there any cases throughout
>>>>>>             the site in which a TOC might run so long that it might
>>>>>>             not fully display within the vertical screen area?  If
>>>>>>             so, I suggest accordion-style B-heads.  Also, a bug:
>>>>>>             you can keep scrolling down once you're at the bottom
>>>>>>             of the content, with more empty space added underneath
>>>>>>             the main content as you go.
>>>>>>
>>>>>>
>>>>>>             On Fri, May 24, 2013 <tel:2013> at 11:13 AM, Lea Verou
>>>>>>
>>>>>>             <lea@w3.org <mailto:lea@w3.org>> wrote:
>>>>>>
>>>>>>                 Hi everyone,
>>>>>>
>>>>>>                 As you might have noticed there are several issues
>>>>>>                 with the TOC pushing down content with clear:both;
>>>>>>                 or content overlapping it (e.g. flags). Yesterday I
>>>>>>                 tried to solve those issues, by moving the TOC
>>>>>>                 outside the content div (but inside the content
>>>>>>                 area) and making it scroll on the free space to the
>>>>>>                 right of the content, as the page is scrolled. Doug
>>>>>>                 suggested I move it outside the content area
>>>>>>                 entirely, so I made a quick mockup which you can
>>>>>>                 find here [1]. It’s not perfect but it should give
>>>>>>                 you a rough idea of how it will look.
>>>>>>                 The issue with that is that it requires a pretty
>>>>>>                 large resolution so we would have to move it in the
>>>>>>                 content area for resolutions < 1440px wide anyway.
>>>>>>                 Also, I don't like the contrast of the dot with the
>>>>>>                 background colors, but this could perhaps be fixed,
>>>>>>                 maybe by tweaking its design a bit. The problem
>>>>>>                 with my original approach is that it makes the
>>>>>>                 content narrower.
>>>>>>
>>>>>>                 Thoughts? Do you prefer this idea or do you think
>>>>>>                 the TOC inside the content area would work better?
>>>>>>
>>>>>>                 [1]:
>>>>>>                 http://docs.webplatform.org/**
>>>>>> test/css/properties/border-**radius<http://docs.webplatform.org/test/css/properties/border-radius>
>>>>>>
>>>>>>                 Lea Verou
>>>>>>                 W3C developer relations
>>>>>>                 http://w3.org/people/all#leahttp://lea.verou.me
>>>>>>                 <http://lea.verou.me/> ✿ @leaverou
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>

Received on Friday, 7 June 2013 17:07:31 UTC