@baris nope, on both
The composer template on lavender is completely unusable on mobile devices
-
-
Definitely not a lot of real estate there....
-
Hm... Tags input could swap text area for an input box?
-
Ouch, thats horrible. What's that, like 5-8 pixels of space to write? Completely unusable there. So lets come up with an idea, and its going to be quite difficult to come to a resolution how you go about solving this UX and UI issue. Looks like to me if you trim the format buttons and tags, you'll be able to see and save roughly 50 pixels or so? Thats still not a lot but hey, its good enough.
Hey @Giorgio-Chiodi can you do me a favor and screenshot Convoe's composer and see what type of result you get as well. I'm not 100% sure of how it looks with that particular phone you have and based on that I can help come up with some clever ideas.
-
Just as a point of comparison... (via Galaxy Nexus)
Stock
SwiftKey
-
@julian That's really weird. we have a couple of nexuses... (nexi?) here they're all stock and we have encountered the same problem. As I told Julian I think it's ok if we hide the text on mobile devices (xs-hidden), than the two buttons go on the formatting bar and we gain some space.
-
@julian Using swiftkey helps though, you gain a couple of pixels.
-
@julian You work from home, yet you're up at 8:30am...
-
@trevor hi here's the screenshot
-
its also happen on my forum too on my Samsung device and if you entered tag first you even cant seen where your text going.
-
I've added a span tag with hidden-xs class but for some weird reason, I can't make nodebb load the right file.
-
@a_5mith said:
@julian You work from home, yet you're up at 8:30am...
Haha I try to keep regular hours... @psychobunny and @baris are the night owls
-
Blah, that sucks then. Thanks again @Giorgio-Chiodi
"Will come up with ideas but too sleepy to try at the moment."
