Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Michael,

please try to work on your quoting, the fullquotes are a very bad habit...

On Fri, Jan 28, 2011 at 2:37 AM, Michael Wheatland
<> wrote:
On Thu, Jan 27, 2011 at 11:25 PM, Christian Lohmaier
<> wrote:
On Thu, Jan 27, 2011 at 12:43 AM, Michael Wheatland

Rimas is correct, I was referring to Silverstripe's behaviour.

This is not silverstripe, but just how javascript behaves.

If this is a non-pluggable part of the Silverstripe UI, I don't expect
you to do anything about it. I just think it is poorly implemented UI
and was looking for other options to improve our experience.

That's bullshit, sorry. When there is a "bug" (in this case in your
eyes a usability bug), it should be fixed.
Calling it "poorly implemented UI" because you have a strong opinion
about it (and others don't care/can live with it) is strongly biased.

Again: Why should there be multiple different UI layers to manage?
That is stupid to do. Have one UI that works and be it. As you might
have noticed in other places, silverstripe is not always using a
javascript prompt. Just that specific feature does.

Seeing your chance to bash silverstripe because of it, great, you got
your fun. Now please get back to being objective and talking in a
reasonable fashion.


Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.