Design issues with the "new" bugzilla interface
Categories
(bugzilla.mozilla.org :: User Interface, defect)
Tracking
()
People
(Reporter: mark, Unassigned)
References
Details
Attachments
(4 files)
Wasted space
While I understand you not wanting to continue supporting 2 interfaces (as explained in the e-mail I received), and with changed for modal styling already bleeding through into the old layout with detrimental effects (like massively oversized input and selection boxes) I have found the modal interface to have a few breaking issues that have prevented me from switching to it. Forcing this now, I'd like to provide some feedback in this bug, since there's only a general feedback to improve channel now with the "legacy" UI being slated for removal. I hope you will consider these points.
- The Modal interface does not make good use of screen space. It has a fixed (rather narrow) width overall, with big blank areas left and right of the main interface that could be used for useful content. People use wide screens. Use that space?
- The modal interface is very much vertically oriented. As a result the header, unless you collapse categories with often essential information, is taking up to 2 screens before actually getting to the bug contents. The old layout is much more compact and efficient with a 2-column header. Once more, people use wide screens. Developers generally don't develop on a vertically-oriented phone or tablet.
- The CC list is a disaster with horizontal and vertical scrollbars and no clear indication of controls. Names have drop-down arrows next to them but they don't do anything and just launch the designated e-mail client...
- "Never e-mail me about this bug" has vanished entirely. No idea where to find that option in the modal UI (is it even still there somewhere?)
- Buttons and input fields are terribly oversized (A recent change?) which often misaligns text.
The result is a (pardon the term) fugly UI that is cumbersome to deal with.
|
||
Comment 1•5 years ago
|
||
- 1/2: The page layout will be 2-column on desktop in Bug 1330451. But the legacy bug page is also not optimized… It was designed when a 1024x768 screen was the majority, and you have to scroll down to see the comments anyway.
- 3: The horizontal scroll will be removed once we start using nicknames entirely. The email issue is Bug 1362951.
- 4: The “Never e-mail me about this bug” option appears once you enter the edit mode. Bug 1248611 will make the UX better, but I personally don’t think it’s a blocker because it’s not often used.
- 5: If it’s a recent change, it’s due to the new skin, so not a blocker. I’m not aware of misaligned text; any example?
|
|
||
Comment 2•5 years ago
|
||
Note: I’m not a designer nor supporter of the modal UI. I still like the legacy UI to be honest. There are many known issues on the modal UI, and I’m more than happy to hear feedback and make the UX better :-)
|
Reporter | |
Comment 3•5 years ago
|
||
- A 2-column layout for the header would make a big difference. I know the old UI is also not optimized but at least it doesn't waste space left/right. The modal UI is fluid up to a point, then it just stops, for no obvious reason. Given, the resulting bug comment area is -slightly- wider than the old UI which had a fixed length catering to monospace fonts (which isn't the best either, of course) but... you're still stopping at 1024 pixels width, making the rest just wasted. Why stop there?
- Misaligned text occurs whenever there is a button or input field present. this is most definitely a skin issue that uses way too much padding for input/form elements, resulting in misalignments
|
|
Reporter | |
Comment 4•5 years ago
|
||
|
|
Reporter | |
Comment 5•5 years ago
|
||
|
|
Reporter | |
Comment 6•5 years ago
|
||
|
|
||
Comment 7•5 years ago
|
||
As I said the layout will be changed in Bug 1330451. The alignment issues are being solved in Bug 1350424. I don’t think those issues are legacy UI decommission blockers, but we are going to solve them soon.
|
|
||
Comment 8•5 years ago
|
||
These dropdown lists are bigger than usual. What browser are you using?
|
||
Comment 10•5 years ago
|
||
Some flavor of Linux most likely. This is what I see on Ubuntu with Gnome window manager.
With my tired eyes, I like the larger controls.
|
|
||
Comment 11•5 years ago
•
|
||
Mark’s browser is apparently Firefox 60 ESR. I could reproduce bigger <select>. It’s still Tier 1 for us, but will be Tier 2 just in 5 weeks once 68 ESR is out, so the minor issue won’t be solved.
|
||
Comment 12•5 years ago
|
||
A bit longer, esr60 will be maintained until 68.2.0esr is out (2019-10-22).
(but I am not saying that we should fix it)
|
|
Reporter | |
Comment 13•5 years ago
|
||
Some flavor of Linux most likely.
Sorry, no. I'm on Windows 7
Mark’s browser is apparently Firefox 60 ESR.
It is not. It's Pale Moon. I know you're going buck at that and try to throw it at "unsupported browser" but not everyone visiting BMO will be using Firefox as their daily driver.
The misalignment is, however, caused by something recent which influences all UI flavors (as it has also messed up the legacy UI). This change is simply that all form elements are now styled with excessive padding (perhaps you are misdetecting the browser based on UserAgent?)
The buttons, for example, are explicitly styled in global.css lines 472 and 601. The browser is doing exactly as it is told, and it's not a browser-side issue.
Look, I have no problem with you retiring the old layout, if the new one is actually fixed up. Don't get me wrong.
|
|
||
Comment 14•5 years ago
•
|
||
Pale Moon is based on Firefox 38 or 52 ESR, maybe? It’s totally fine to use a non-Firefox browser on BMO (there are many Chrome users here) but old browsers are not supported, unfortunately. See our browser requirements. Only the latest ESR is Tier 1, so Firefox 60 ESR is moving to Tier 2 once 68 ESR is out.
The text alignment issue is not new; it has existed in the legacy UI too.
The <select> widget size cannot be fixed, but the layout/whitespace and alignment issues will be solved soon, hopefully before the legacy UI retires.
|
|
Reporter | |
Comment 15•5 years ago
•
|
||
Pale Moon is based on Firefox 38 or 52 ESR, maybe?
Neither. The application code is its own.
It's also not an "old browser", it's constantly updated. I really wish people would stop parroting the haters of Pale Moon, Basilisk and other applications building on the platform we're maintaining. It may be a small market browser (slightly more usership than SeaMonkey) but it's not old. Please don't confuse the two.
As said above though, this is NOT a client issue, as the alignment issues are clearly resulting from explicitly defined CSS rules in the modal design. If I disable the explicit 5px padding rules top and bottom, everything falls into place just fine.
If there is an issue with our widget code for <select> form elements (but I'm not sure what you are referring to there), then please let me know and I can look into improving it.
It’s totally fine to use a non-Firefox browser on BMO
"as long as it's the latest version of Firefox and chrome derivatives". Sorry, please don't kid yourself. It's also totally fine to design a bugtracker layout in such a way that it looks good on all browsers instead of using quirks from the latest drafts that people cook up.
The text alignment issue is not new; it has existed in the legacy UI too.
It is new. It is since form elements were enlarged with styling which is a relatively recent development. Previously they would use the OS default styling which worked just fine.
|
|
||
Updated•5 years ago
|
|
||
Comment 16•5 years ago
|
||
(In reply to Mark Straver from comment #15)
Pale Moon is based on Firefox 38 or 52 ESR, maybe?
Neither. The application code is its own.
It's also not an "old browser", it's constantly updated. I really wish people would stop parroting the haters of Pale Moon,
Identifying specific browsers nothing to do with hating so no need to bring it up. Sure, Pale Moon has been updated. And no one is saying it is a bad browser. But the facts are it's a fork - per http://kmeleonbrowser.org/forum/read.php?1,141148 Pale Moon was rebased from Gecko 38. More at https://www.palemoon.org/technical.shtml
That said, Kohei is very responsive to addressing issues that affects all browsers
|
|
||
Comment 17•5 years ago
|
||
This isn't the place to chat about Pale Moon, please take the conversation somewhere else :)
|
|
||
Comment 18•5 years ago
|
||
I’d go ahead to close the bug for now. Mark’s points in Comment 0 are valid but covered in other bugs, and this “general feedback” bug itself is not actionable. Unfortunately we can’t fix issues specific to Pale Moon, which is in fact a fork of a very old Gecko version. Thanks Mark anyway, I’m always happy to hear from real users!
|
|
Reporter | |
Comment 19•5 years ago
|
||
Unfortunately we can’t fix issues specific to Pale Moon, which is in fact a fork of a very old Gecko version.
Stop perpetuating that nonsense please. I should know because I'm the project owner of it!
I know this isn't the place to discuss Pale Moon but if you're going to post such misinformation in a public place I have to respond. You're incorrect about Pale Moon. Get it through your skull and stop echoing what others keep stating when they either (1) don't know what they are talking about, (2) base their information on old posts or (3) do all this on purpose to try and paint Pale Moon black (unfortunately more common than one might think in the Firefox fanboi corner)
|
||
Updated•5 years ago
|
Description
•