Are you sure? Maybe some time later, youāll be sad about this decision
Getting back to this and doing some testingā¦ I actually canāt get the edit conflict
error to show at all nowā¦ Not sure if this is related to your changes @venarius (canāt see anything obvious) or something elseā¦
Hereās how Iām trying to trigger it:
- User A opens composer to edit wiki post (revision 1)
- User B opens composer to edit same wiki post (revision 1)
- User A saves revision
- User B attempts to save revision
Iām seeing the normal saving/saved draft icons in Step 4 both before and after I attempt to save the revision. The modal warning User B that theyāre about to overwrite an edit appears correctly.
I tested locally and on Meta and canāt get the edit conflict message to appear. Am I missing something? Can someone else double check?
@nbianca can you verify this did not regress?
Still not able to trigger the edit conflict, but that seems to be a separate issue.
Preview button is moved here
https://github.com/discourse/discourse/commit/c57ab12238b85211b4750595b3325d98311102be
Why is image button below on mobile and not in toolbar like on desktop? I find this a bit confusingā¦
Itās an important action that isnāt easy to do on mobile without a button, and sometimes the toolbar isnāt visible on mobile (I think the toolbar also used to be hidden more often than it is today) - so it gets called out in a special way.
I could see how it would be confusing if youāre used to the desktop layout, until recently we had the button in both places, which would cover that familiarityā¦ but we didnāt like the redundancy
How could you revert the change of location for the preview button?
But why is hiding toolbar still a thing on mobile? I ālostā it once and thought it was a bug at first, that it did not show up anymore. Is really vertical space so big of an issue on mobile, that is worth this complicated UX?
Yes, Android phones can have tiny screens. There are zillions of different Android devices.
It seems that option 2 (Add preview button next to image upload) was implemented. Iād like to share a couple of observations related to the resulting UX:
-
A user on my forum (quite a web-savvy guy) simply could not for the life of himself figure out where the formatting toolbar had gone, to the point where he reached out to me thinking its absence had been caused by a bug. It looks like plans to conditionally make the toolbar appear on Android devices were not followed upon; would it be possible for this idea to be revisited and perhaps implemented?
-
Additionally (or alternatively), a setting that would allow to switch off the toolbar auto-collapse feature altogether, and/or to define its default state on all devices would be greatly appreciated.
-
The button that controls the display and collapse of the toolbar is a hamburger menu button, and this is an additional hindrance to discoverability. Itās also odd, given that there no longer are actual menu items behind this button, only a single, immediate action. Could the icon be changed to something a bit more on point? Maybe a straight ruler? Or a pencil?