If the category name is too long, the tag button gets cut off.
Is it possible to show a numerical count of tags added after 1 or more tags are added, next to the icon? That seems better than having the tag icon filled now (it’s very subtle).
I think Canapin brought this up: the title feels quite cut off for some reason; it might have to do with the floating button in the way.
When enabling Composer Redesign. Choosing Staff or Specific Groups did not work. I had to choose everyone
I didn’t see an error but can try retesting i first tried to set it to specific groups Staff, Guide
When I tested composer it was unchanged. So I tried the Staff only option with same effect. Only once I enabled for everyone did it show the redesigned composer in mobile
I haven’t tested in desktop. I apologize as I forgot to add extra details
Mobile on Google Pixel 9 XL.
EDiT just retried those settings. Working now! May have been viewing cached forum? I had even tried refreshing. But all good now
Very minor design oversight. When active, the selector’s background has rounded border whereas there aren’t visible rounded borders on the default state:
I know this has been said before but I really hope the preview button can be brought back on mobile. One of the forums I use doesn’t have enough community push to install the component workaround.
It’s kinda flashy, and flashes blue when expanding due to the Chromium-characteristic blue highlight(?).
Besides that I need to tap the minus button twice to minimize when keyboard is launched. (note: not present in old design) This might be caused by this glitch in this video frame (seen after tapping minus button the first time), where the URL bar jumps up to the position of minus button for unknown reason:
It seems to work well on Foundation, but there are some issues on Horizon: the preview window has a border with the accent color.
Glad it works well on Foundation! For Horizon, Yes I know, as I said in OP
Im still working on it.
I asked AI and the blue flash can be fixed by adding -webkit-tap-highlight-color: transparent to the element in question. I’d recommend doing that for the editor element because when it occupies full screen when expanding, it results in fullscreen flash, not good visual feel.
This is how it looks like if I apply * {-webkit-tap-highlight-color: transparent} with Stylus (I’m using Edge on Android)
I think the borderless design is significantly less intuitive:
The title appears to be part of the post body editor. Fine. But if I type the title and then press the Enter key, the cursor doesn’t move to the next line. It feels like I’m just stuck on the first line of the post without any way to progress. I don’t think the user will intuitively understand they must click on the next line or press Tab to continue. If you want to make title input part of the post body editor, then it must work just like any other line in the editor. If it is going to continue to be treated as a separate input field, then go back to the old design where that nature was visually communicated to the user.
The lack of a border between the post editor and the preview (when the composer is in markdown editor mode) is too confusing. These are two separate panels. That fact should be visually communicated to the user by a border between the two.
There is no right margin on the preview that is shown when the composer is in “markdown editor mode”:
I would expect it to have a margin similar to the one we see on the left side of the composer, as we see when the composer is in “rich text editor mode”:
@renato Do you think that’s easy enough to achieve?
If it does, should it also go the other way? If the cursor is at the beginning of the textarea, pressing back should go to the title input then?
Those being distinct fields, I’d find this whole behavior (title to textarea and vice versa) bizarre, but perhaps I’d change my mind after using it.
Just FYI, and perhaps too soon and already known, but the toolbar is totally missing when using mobile/iPhone on DiscourseHub
Edit
It has nothing to do with DiscourseHub. It follows visibility status of the the toolbar of original composer.
If the toolbar is hided via the toggle, and then new composer is enabled, the toolbar isn’t visible and there is no way AFAIK to show it. And vice versa. If original one has visible toolbar, then changing to new composer offers the toolbar.
