Andrei Alexandrescu:

> I think we're in a better place than before.

If the browser detects no JavaScript it can present a simpler alternative but usable menu.

Bye,
bearophile

On Tuesday, 20 January 2015 at 07:21:31 UTC, Phil wrote:
> Pull 790 would be a big improvement . The current page also doesn't seem to be working properly. The right margin is empty except for a link to the D Twitter feed at the very top. I assume there's supposed to be a widget there showing tweets like before (although I never liked that).

Perhaps an ad blocker or something similar is preventing it from showing up in your browser?

See if it works in a different browser.

On Tuesday, 20 January 2015 at 13:44:09 UTC, Steven Schveighoffer wrote:
> On 1/19/15 10:29 PM, Andrei Alexandrescu wrote:
>> * New docs don't yet have the new menu implemented.
>
> Also forums.

I'll get to that once the design stabilizes.

On Tuesday, 20 January 2015 at 15:41:30 UTC, bearophile wrote:
> Andrei Alexandrescu:
>
>> I think we're in a better place than before.
>
> If the browser detects no JavaScript it can present a simpler alternative but usable menu.

All expandable sections should show up as expanded when no JS is
available.

On Tuesday, 20 January 2015 at 03:36:16 UTC, Andrei Alexandrescu wrote:
> On 1/19/15 7:34 PM, Vladimir Panteleev wrote:
>> On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole wrote:
>>> Say ugh, when was the last time somebody clicked the ol' "Page wiki"
>>> buttons.
>>> Because atleast for intro, it doesn't exist.
>>
>> They don't need to all exist. The idea is to link to a page that anyone
>> can create, and then anyone else can get to by clicking the same link in
>> the page header.
>
> I fear that newcomers finding many of those page unpopulated would think there's no activity etc. -- Andrei

I could run a script to populate them with a placeholder.

These pages were numerous on the old wiki, and although we could look into migrating them, most information is likely outdated by now.

Vladimir Panteleev:

> All expandable sections should show up as expanded when no JS is
> available.

But currently they aren't doing that, right?

Bye,
bearophile

On Tuesday, 20 January 2015 at 16:31:12 UTC, bearophile wrote:
> Vladimir Panteleev:
>
>> All expandable sections should show up as expanded when no JS is
>> available.
>
> But currently they aren't doing that, right?

They are. It is working for me when I disable JS in Firefox (via about:config).

If it doesn't work for you, how can I reproduce the problem?

On 1/20/15 7:41 AM, bearophile wrote:
> Andrei Alexandrescu:
>
>> I think we're in a better place than before.
>
> If the browser detects no JavaScript it can present a simpler
> alternative but usable menu.

Yah, it leaves all submenus open. -- Andrei

Vladimir Panteleev:

> If it doesn't work for you, how can I reproduce the problem?

Today browsers are terribly complex, there's little hope to reproduce an environment. So never mind, ignore my precedent comment...

Bye,
bearophile

On 1/20/15 8:33 AM, Vladimir Panteleev wrote:
> On Tuesday, 20 January 2015 at 16:31:12 UTC, bearophile wrote:
>> Vladimir Panteleev:
>>
>>> All expandable sections should show up as expanded when no JS is
>>> available.
>>
>> But currently they aren't doing that, right?
>
> They are. It is working for me when I disable JS in Firefox (via
> about:config).
>
> If it doesn't work for you, how can I reproduce the problem?

There was a bug for a while that hid everything. Might be a matter of refreshing. -- Andrei