On Mon, 26 Jan 2015 02:36:29 +0000, Vladimir Panteleev wrote:

> On Monday, 26 January 2015 at 02:13:44 UTC, ketmar wrote:
>> On Mon, 26 Jan 2015 02:00:01 +0000, Laeeth Isharc wrote:
>>
>>> Imagine you move from a javascript browser to one without
>> dlang.org is imfunctional without js, so there is no sense to make anything else working right without js.
> 
> dlang.org should work just fine without JS. Same goes for the forums, but of course you won't be able to use the JS-powered horizontal-split view mode.

yet it doesn't work: side menu is not working anymore, which renders dlang.org completely unusable for me.

On Monday, 26 January 2015 at 03:14:00 UTC, ketmar wrote:
> On Mon, 26 Jan 2015 02:36:29 +0000, Vladimir Panteleev wrote:
>
>> On Monday, 26 January 2015 at 02:13:44 UTC, ketmar wrote:
>>> On Mon, 26 Jan 2015 02:00:01 +0000, Laeeth Isharc wrote:
>>>
>>>> Imagine you move from a javascript browser to one without
>>> dlang.org is imfunctional without js, so there is no sense to make
>>> anything else working right without js.
>> 
>> dlang.org should work just fine without JS. Same goes for the forums,
>> but of course you won't be able to use the JS-powered horizontal-split
>> view mode.
>
> yet it doesn't work: side menu is not working anymore, which renders
> dlang.org completely unusable for me.

Everything works for me. The menu is completely expanded without JS, providing access to all areas of the website.

Please explain what exactly doesn't work.

On Mon, 26 Jan 2015 03:17:54 +0000, Vladimir Panteleev wrote:

> On Monday, 26 January 2015 at 03:14:00 UTC, ketmar wrote:
>> On Mon, 26 Jan 2015 02:36:29 +0000, Vladimir Panteleev wrote:
>>
>>> On Monday, 26 January 2015 at 02:13:44 UTC, ketmar wrote:
>>>> On Mon, 26 Jan 2015 02:00:01 +0000, Laeeth Isharc wrote:
>>>>
>>>>> Imagine you move from a javascript browser to one without
>>>> dlang.org is imfunctional without js, so there is no sense to make anything else working right without js.
>>> 
>>> dlang.org should work just fine without JS. Same goes for the forums, but of course you won't be able to use the JS-powered horizontal-split view mode.
>>
>> yet it doesn't work: side menu is not working anymore, which renders dlang.org completely unusable for me.
> 
> Everything works for me. The menu is completely expanded without JS, providing access to all areas of the website.
> 
> Please explain what exactly doesn't work.

it's collapsed by default, and there is no way to expand it. http://ketmar.no-ip.org/2015-01-26-05-24-35_809x525.png

i don't really know what goes wrong there, nor i want to investigate the issue. maybe it's due to blocked google sites (same origin policy+strict "no requests to google" policy) plus flawed script blocker which misses some page scripts that using jquery, just enough to collapse the menu, but not enough to expand it. the fact is that previous version was working just fine and new one is completely broken.

On Monday, 26 January 2015 at 03:17:55 UTC, Vladimir Panteleev wrote:
> On Monday, 26 January 2015 at 03:14:00 UTC, ketmar wrote:
>> On Mon, 26 Jan 2015 02:36:29 +0000, Vladimir Panteleev wrote:
>>
>>> On Monday, 26 January 2015 at 02:13:44 UTC, ketmar wrote:
>>>> On Mon, 26 Jan 2015 02:00:01 +0000, Laeeth Isharc wrote:
>>>>
>>>>> Imagine you move from a javascript browser to one without
>>>> dlang.org is imfunctional without js, so there is no sense to make
>>>> anything else working right without js.
>>> 
>>> dlang.org should work just fine without JS. Same goes for the forums,
>>> but of course you won't be able to use the JS-powered horizontal-split
>>> view mode.
>>
>> yet it doesn't work: side menu is not working anymore, which renders
>> dlang.org completely unusable for me.
>
> Everything works for me. The menu is completely expanded without JS, providing access to all areas of the website.
>
> Please explain what exactly doesn't work.

It's broken if dlang.org is allowed yet ajax.googleapis.com is disallowed. Thus anyone who blocks google yet has dlang.org enabled (e.g. for the links in docs) is unable to use the menus.

On Monday, 26 January 2015 at 03:31:15 UTC, ketmar wrote:
> i don't really know what goes wrong there, nor i want to investigate the
> issue. maybe it's due to blocked google sites (same origin policy+strict
> "no requests to google" policy) plus flawed script blocker which misses
> some page scripts that using jquery, just enough to collapse the menu,
> but not enough to expand it. the fact is that previous version was
> working just fine and new one is completely broken.

I see. Your issue is not that JS is disabled, it is that you are selectively blocking components of the webpage.

As with any system, it is not unusual that it stops working as designed when you rip out arbitrary parts of it.

I see no reason to support such a configuration in principle, but for this particular case, I think the fix will be simple.

On Mon, Jan 26, 2015 at 03:34:56AM +0000, Kiith-Sa via Digitalmars-d wrote:
> On Monday, 26 January 2015 at 03:17:55 UTC, Vladimir Panteleev wrote:
> >On Monday, 26 January 2015 at 03:14:00 UTC, ketmar wrote:
> >>On Mon, 26 Jan 2015 02:36:29 +0000, Vladimir Panteleev wrote:
> >>
> >>>On Monday, 26 January 2015 at 02:13:44 UTC, ketmar wrote:
> >>>>On Mon, 26 Jan 2015 02:00:01 +0000, Laeeth Isharc wrote:
> >>>>
> >>>>>Imagine you move from a javascript browser to one without
> >>>>dlang.org is imfunctional without js, so there is no sense to make anything else working right without js.
> >>>
> >>>dlang.org should work just fine without JS. Same goes for the forums, but of course you won't be able to use the JS-powered horizontal-split view mode.
> >>
> >>yet it doesn't work: side menu is not working anymore, which renders dlang.org completely unusable for me.
> >
> >Everything works for me. The menu is completely expanded without JS, providing access to all areas of the website.
> >
> >Please explain what exactly doesn't work.
> 
> It's broken if dlang.org is allowed yet ajax.googleapis.com is disallowed.  Thus anyone who blocks google yet has dlang.org enabled (e.g. for the links in docs) is unable to use the menus.

Shouldn't it be expanded by default and collapsed if JS is available?


T

-- 
Doubt is a self-fulfilling prophecy.

On Mon, 26 Jan 2015 03:35:02 +0000, Vladimir Panteleev wrote:

> I see. Your issue is not that JS is disabled, it is that you are selectively blocking components of the webpage.
> 
> As with any system, it is not unusual that it stops working as designed when you rip out arbitrary parts of it.
>
> I see no reason to support such a configuration in principle, but for this particular case, I think the fix will be simple.

yet there is increasing movement towards "same origin policy" as a part of overall privacy concerns, so i believe that such things will start popping up here and there.

On Sun, 25 Jan 2015 19:37:00 -0800, H. S. Teoh via Digitalmars-d wrote:

> Shouldn't it be expanded by default and collapsed if JS is available?

my uneducated guess is that "collapser" is not using jquery, so it was able to successfully collaspe the whole thing. and then "expander" is using jquery, so it failed.

On Monday, 26 January 2015 at 03:35:03 UTC, Vladimir Panteleev wrote:
> I see no reason to support such a configuration in principle, but for this particular case, I think the fix will be simple.

Actually, I take that back. There are good reasons to support such a situation, the biggest of which is that Google CDNs are blocked in China:

https://issues.dlang.org/show_bug.cgi?id=14004

https://github.com/D-Programming-Language/dlang.org/pull/847

On Monday, 26 January 2015 at 03:43:53 UTC, ketmar wrote:
> On Sun, 25 Jan 2015 19:37:00 -0800, H. S. Teoh via Digitalmars-d wrote:
>
>> Shouldn't it be expanded by default and collapsed if JS is available?
>
> my uneducated guess is that "collapser" is not using jquery, so it was
> able to successfully collaspe the whole thing. and then "expander" is
> using jquery, so it failed.

Actually, we inject a CSS rule based on whether JS is enabled or not. We can't check for jQuery there because its loading is deferred.