On Friday, 5 June 2015 at 01:39:48 UTC, Manu wrote:
> If I click to select some text, the page bounces downwards on the
> mouse-up event.
> If I click again to select some other text, the page bounces back
> upwards again to it's original position (again, on the mouse-up).

How do I reproduce this? What browser, view mode, etc.? I don't think I do anything fancy with mouse events...

On 5 June 2015 at 11:39, Manu <turkeyman@gmail.com> wrote:
> On 5 June 2015 at 01:04, Vladimir Panteleev via Digitalmars-d-announce <digitalmars-d-announce@puremagic.com> wrote:
>> http://beta.forum.dlang.org/
>>
>> Many major and minor improvements.
>>
>> Some major ones:
>>
>> - dlang.org theme, fully responsive and mobile-friendly
>> - keyboard navigation in all views
>> - automatically saved post drafts
>> - get notified of new posts and replies with subscriptions
>> - full text search
>> - by persistent request, a new view mode (vertical-split)
>> - post to mailing lists
>> - even faster, believe it or not.
>>
>> This update is the sum of 256 commits over 34 days of development.
>
> Awesome stuff! Looks great, and it's fast!
>
> Incidentally, I have a bug.
> If I click to select some text, the page bounces downwards on the
> mouse-up event.
> If I click again to select some other text, the page bounces back
> upwards again to it's original position (again, on the mouse-up).

Also, oauth?
There is no way I would register an account to make a post unless I
was *really* motivated.
It may be that we have lost potential participants because they
clicked away from the page within seconds of realising there was no
oauth (I definitely would).

On Friday, 5 June 2015 at 01:42:20 UTC, Manu wrote:
> Also, oauth?
> There is no way I would register an account to make a post unless I
> was *really* motivated.

What gave you the impression that you have to register an account in order to post? The front page now explicitly says that you don't need an account to post.

> It may be that we have lost potential participants because they
> clicked away from the page within seconds of realising there was no
> oauth (I definitely would).

It's doable but just seems a little overkill to me. Every time I looked into implementing OAuth I was swamped by how overly complicated it was (or maybe I just never found a succint-enough description).

On Thursday, 4 June 2015 at 15:04:05 UTC, Vladimir Panteleev wrote:
> http://beta.forum.dlang.org/
>
> Many major and minor improvements.
>
> Some major ones:
>
> - dlang.org theme, fully responsive and mobile-friendly
> - keyboard navigation in all views
> - automatically saved post drafts
> - get notified of new posts and replies with subscriptions
> - full text search
> - by persistent request, a new view mode (vertical-split)
> - post to mailing lists
> - even faster, believe it or not.
>
> This update is the sum of 256 commits over 34 days of development.

How feasible is it to add code formatting for the web interface?

On 5 June 2015 at 11:42, Vladimir Panteleev via Digitalmars-d-announce <digitalmars-d-announce@puremagic.com> wrote:
> On Friday, 5 June 2015 at 01:39:48 UTC, Manu wrote:
>>
>> If I click to select some text, the page bounces downwards on the
>> mouse-up event.
>> If I click again to select some other text, the page bounces back
>> upwards again to it's original position (again, on the mouse-up).
>
>
> How do I reproduce this? What browser, view mode, etc.? I don't think I do anything fancy with mouse events...

Win8.1, Chrome latest, nothing special about the view configuration. Here is a link: http://beta.forum.dlang.org/post/poefipvtjbcpnkopktja@forum.dlang.org I don't know if this link is special... just click on the screen somewhere and watch it bounce around.

On Friday, 5 June 2015 at 01:48:20 UTC, Meta wrote:
> How feasible is it to add code formatting for the web interface?

Not sure what you mean. Do you mean syntax highlighting for D code?

If you mean the rewrapping issues with forum.dlang.org, those should be fixed now. Code (and other text with hard line breaks) should be sent and displayed as-is.

On Friday, 5 June 2015 at 01:52:07 UTC, Vladimir Panteleev wrote:
> On Friday, 5 June 2015 at 01:48:20 UTC, Meta wrote:
>> How feasible is it to add code formatting for the web interface?
>
> Not sure what you mean. Do you mean syntax highlighting for D code?
>
> If you mean the rewrapping issues with forum.dlang.org, those should be fixed now. Code (and other text with hard line breaks) should be sent and displayed as-is.
Sorry if this question has been raised but is the reason for the inability to edit posts? Will be this feature implemented sometime?

On Friday, 5 June 2015 at 02:02:11 UTC, IgorStepanov wrote:
> Sorry if this question has been raised but is the reason for the inability to edit posts?

Posts are not editable because once sent, they are relayed to the NNTP server, mailing lists, and users' email inboxes.

> Will be this feature implemented sometime?

Only when it becomes possible to edit a sent email.

On Friday, 5 June 2015 at 01:49:31 UTC, Manu wrote:
> On 5 June 2015 at 11:42, Vladimir Panteleev via Digitalmars-d-announce <digitalmars-d-announce@puremagic.com> wrote:
>> On Friday, 5 June 2015 at 01:39:48 UTC, Manu wrote:
>>> [...]
>>
>>
>> How do I reproduce this? What browser, view mode, etc.? I don't think I do anything fancy with mouse events...
>
> Win8.1, Chrome latest, nothing special about the view configuration. Here is a link: http://beta.forum.dlang.org/post/poefipvtjbcpnkopktja@forum.dlang.org I don't know if this link is special... just click on the screen somewhere and watch it bounce around.

Ah, fixed, thanks.

On Friday, 5 June 2015 at 01:52:07 UTC, Vladimir Panteleev wrote:
> On Friday, 5 June 2015 at 01:48:20 UTC, Meta wrote:
>> How feasible is it to add code formatting for the web interface?
>
> Not sure what you mean. Do you mean syntax highlighting for D code?
>
> If you mean the rewrapping issues with forum.dlang.org, those should be fixed now. Code (and other text with hard line breaks) should be sent and displayed as-is.

Syntax highlighting is always nice, but yeah, I more meant the line wrapping issues.