I have a different opinion. This modality issue is not something we fix as a bug. Of course, we can put in place a patch that somehow makes it work in the current browser, but the core problem is a conceptual one. And that requires a redesign of the user interface.

If we have a problem with a code model, we do not just put an if to patch the thing. Ok, sometimes we do that just because we cannot see a different solution, but we are not comfortable with it. We have to treat the user interface in the same way.

Doru

On Wed, Sep 4, 2013 at 9:56 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

On Sep 3, 2013, at 9:27 PM, St��phane Ducasse <stephane.ducasse@inria.fr> wrote:

> agreed we should change that since years.
> Some days we should stop and fix all the glitches that give us these hiccups.

... and that day is around october, when we freeze pharo3 and start to fix bugs :)

Esteban

>
> stef
>
> On Sep 3, 2013, at 3:07 PM, Igor Stasenko <siguctua@gmail.com> wrote:
>
>>
>> this is most annoying to me, that UI interrupts you in very strange manner
>> and asks you to make a decision:
>> - accept, or discard the method, or cancel the action.
>>
>> often, you are in the middle of typing new stuff and source code
>> can be even not syntactically correct.. so, you have to discard or die :)
>>
>> what i think the solution could be is that browser should allow you to switch contexts
>> at any moment without asking you anything.Instead it should remember your
>> unsaved changes in special 'drafts' collection, which later you can get back on,
>> when you finish what you wanted to do.
>>
>> And the only time when you want unaccepted edits to not get lost forever is when you closing
>> a browser window.. (but of course, drafts can be stored globally somewhere,
>> then it also not a big deal, since you can simply return to your draft in different window).
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>
>

--

www.tudorgirba.com

"Every thing has its own flow"