Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#16 2012-03-30 14:16:55

phiw13
Plugin Author
From: South-Western Japan
Registered: 2004-02-27
Posts: 3,631
Website

Re: r3661 error when saving an new article

wet wrote:

Thanks. We surely want to. Try r3698.

Is that actually working ? I trying saving a form on the sections tab and absolutely nothing happens – visually, I mean [*]. All the save buttons ‘grey out’ (that is the theme style), but I don’t see any actual ‘saving’. On the write page the same issue.
Watching through Safari’s WebInspector, the class ‘busy’ is applied but never removed.

[*] and it doesn’t matter how I access the save button – keyboard or mouse click.


Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg

Offline

#17 2012-03-30 15:21:08

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,565
Website GitHub Mastodon

Re: r3661 error when saving an new article

Adding to what Philippe said, there also needs to be visual feedback that a success action has happened -when there is an error message the div pulses a couple of times to draw the eye, but when there is a success message that does not happen, so is easily missed and can make the user wonder if an action has actually happened (the alert messages in the core themes are also not obvious enough either IMHO but that’s not for this thread).

I’ve worked around that in my own 4.5 admin theme, but it should be noted in the core admin theme too.

Last edited by philwareham (2012-03-30 15:21:47)

Offline

#18 2012-03-30 16:52:24

wet
Developer Emeritus
From: Vöcklabruck, Austria
Registered: 2005-06-06
Posts: 3,416
Website GitHub Mastodon

Re: r3661 error when saving an new article

phiw13 wrote:

Is that actually working ?

Works for me. Looks like this change set broke in Safari. Fixed in r3699.

philwareham wrote:

…there also needs to be visual feedback that a success action has happened

This might be a need for a fraction of users. But I’m quite sure that others will find such an indication useless or even distracting once they have acquainted to the non-obtrusive procedure of intermediate saves while they write a longish article. Less distraction is one reason why we want AJAX on the write tab.

There’s some popular software which handles successes rather silently. Try saving a document in LibreOffice Calc (progress bar), or saving a widget’s options in WordPress (spinner).

I think that “success” is the default outcome of any user operation, and we shouldn’t make much ado about this non-event. Other may think the opposite, and this is why Textpattern has this theming capability.

Last edited by wet (2012-03-30 19:24:06)

Offline

#19 2012-03-30 17:14:18

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,565
Website GitHub Mastodon

Re: r3661 error when saving an new article

Fair enough. Maybe it’s that the success message is permanently there after the first save, but it doesn’t feel right to me. Anyway, as you say it’s totally themeable so not really an issue.

Also, maybe it’s because txp is so fast – I never see the spinner more than about a millisecond! That’s a good thing.

Last edited by philwareham (2012-03-30 17:16:25)

Offline

#20 2012-03-31 00:40:02

phiw13
Plugin Author
From: South-Western Japan
Registered: 2004-02-27
Posts: 3,631
Website

Re: r3661 error when saving an new article

wet wrote:

Works for me. Looks like this change set broke in Safari. Fixed in r3699.

Yep, now everything works fine, no matter how I access the submit button (tested Gecko 1.9.2 and WebKit/Safari).


Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg

Offline

Board footer

Powered by FluxBB