Responsive Redesign: Mobile "Question Details" and "Question Tools"
Categories
(support.mozilla.org :: Questions, defect)
Tracking
(Not tracked)
People
(Reporter: seburo3, Assigned: lmcardle)
References
Details
Attachments
(1 file)
191.98 KB,
image/jpeg
|
Details |
In the current live design, if I want to see the Question Details or the Question Tools, I can use the desktop mode in the browser (Fenix Nightly) to see them.
In the current responsive redesign on staging, I cannot see this information or have access to these tools either in a mobile view or desktop view. This will make it much harder for me to answer questions and support users - the site is less mobile responsive.
Please can this be fixed as a priority?
Assignee | ||
Comment 1•5 years ago
|
||
They are there, but hidden under the "Related" drop-down at the top of the page. It took me quite a while to find this, so I think we could do with a copy change here.
I hope that nobody minds me reopening this, but having used the new layout for a while, there is a change that I believe needs to be made.
Look at the attached screenshot, it would be good if some of the white space between the tags and "Add a tag" was reduced, as would (more importantly) the space between "Add a tag" and "Question Details". This would have the effect of making the "Question Details" more visible and easier for a contributor answering questions on the support forum to see them.
Comment 4•2 years ago
|
||
Hey Seburo!
I know that it has been a long time since this issue was initially filled.
I just checked and the "Question Tools" menu is visible so I guess that the issue mentioned in comment 0 is now fixed?
If you believe that the adjustments from comment 3 are still required we can morph this ticket or better yet, track it in a different enhancement ticket.
Hi Emil
Yes, the question tools issue is fixed and looks great. There is still a white space issue in respect of mobile that would be good to get resolved, preferably in a morphed ticket.
Updated•2 years ago
|
Updated•7 months ago
|
Comment 6•1 month ago
|
||
Hi Seburo!
This issue was fixed in our latest release.
Please feel free to re-open this ticket if this is still reproducible on your end!
Description
•