All users were logged out of Bugzilla on October 13th, 2018

"We've made a guess" note on enter_bug comes *after* the fields it's about

RESOLVED FIXED in Bugzilla 4.0



10 years ago
9 years ago


(Reporter: mkanat, Assigned: mkanat)


(Blocks: 1 bug)

Bugzilla 4.0
Dependency tree / graph


(Whiteboard: [fixed by blocker])


(1 attachment)



10 years ago
In pryzak's students' research, they noticed that the "We've made a guess at your operating system and platform" note shows up after the OS and Platform fields, in a position that's kind of removed from them. Instead it should probably be near (maybe to the side) of the fields.

Comment 1

9 years ago
Created attachment 412696 [details] [diff] [review]
move "we made a guess" to the side of the fields it refers to v1

This moves the text. This change involves making the create bug table 5 columns wide. There may be a better way, but this looks OK to me.
Assignee: create-and-change → bugzilla
Attachment #412696 - Flags: review?

Comment 2

9 years ago
The only reason I'm hesitant about accepting this is that we actually want to move the OS/Platform auto-detection code into an extension, so changing the number of columns in the create form to accommodate it right now isn't something I'm sure I want to do.

Comment 3

9 years ago
The "we guessed" message could be moved to under the field label, or under the label and field, or there may be an argument for removing the "we guessed" message, as most people will not read it, need it, or heed it.

Comment 4

9 years ago
Comment on attachment 412696 [details] [diff] [review]
move "we made a guess" to the side of the fields it refers to v1

I agree that we don't want an additional column for that. It should be below the OS + platform fields, which is done by bug 490766.
Attachment #412696 - Flags: review? → review-

Comment 5

9 years ago
Fixed by bug 490766.
Assignee: bugzilla → mkanat
Last Resolved: 9 years ago
Depends on: 490766
Resolution: --- → FIXED
Whiteboard: [fixed by blocker]
Target Milestone: --- → Bugzilla 3.8
You need to log in before you can comment on or make changes to this bug.