Closed
Bug 460372
Opened 17 years ago
Closed 13 years ago
The confirmation thrown when deleting a custom field, component, version or product must have a red background if the deletion affects bugs
Categories
(Bugzilla :: Administration, task)
Tracking
()
RESOLVED
FIXED
Bugzilla 4.4
People
(Reporter: LpSolit, Assigned: sjoshi)
References
Details
Attachments
(1 file, 6 obsolete files)
|
3.87 KB,
patch
|
LpSolit
:
review+
|
Details | Diff | Splinter Review |
All other administrative confirmations displayed when deleting a value have a red background, because data loss may happen. When you delete a custom field, the confirmation has no red background. I barely pay attention to it despite it's a rather important message. It should use the same class as other confirmations.
| Reporter | ||
Updated•17 years ago
|
Whiteboard: [Good Intro Bug]
Patch generated using "diff", not cvs.
After examining Bugzilla's stylesheets, the class "areyoureallysure" seemed to be the one to use here.
| Reporter | ||
Comment 2•17 years ago
|
||
Comment on attachment 363147 [details] [diff] [review]
Adds CSS class to warning text
This class doesn't exist.
Attachment #363147 -
Flags: review-
Re-examined the directory tree. The class "throw_error" in skins/standard/global.css has the style settings I remembered (red background in slightly larger font size with extra padding) from the class I thought existed. Let's go with that.
Attachment #363147 -
Attachment is obsolete: true
Comment 4•17 years ago
|
||
Attachment #377655 -
Flags: review?(LpSolit)
| Reporter | ||
Updated•17 years ago
|
Attachment #364726 -
Attachment is patch: true
Attachment #364726 -
Attachment mime type: application/octet-stream → text/plain
| Reporter | ||
Comment 5•17 years ago
|
||
Comment on attachment 364726 [details] [diff] [review]
Corrects senior moment on CSS class added previously
We should have a separate class for such warning. throw_error displays the text as bold and bigger, which is not necessary here. Also, this class should be used everywhere, for such warnings.
Attachment #364726 -
Flags: review-
| Reporter | ||
Updated•17 years ago
|
Attachment #377655 -
Flags: review?(LpSolit) → review-
| Reporter | ||
Comment 6•17 years ago
|
||
Comment on attachment 377655 [details] [diff] [review]
added admin.css and used the class "areyoureallyreallysure"
Not the right class. Text is red, not the background.
Comment 7•17 years ago
|
||
I looked at the confirmations while deleting a classification and deleting a keyword, but they don't have a class with a red background.
Should I modify the areyoureallyreallysure class to have a red background and black text?
| Reporter | ||
Comment 8•17 years ago
|
||
(In reply to comment #7)
> Should I modify the areyoureallyreallysure class to have a red background and
> black text?
No, this class should be left alone. A new class is needed.
Comment 9•17 years ago
|
||
Attachment #377655 -
Attachment is obsolete: true
Attachment #379831 -
Flags: review?(LpSolit)
| Reporter | ||
Updated•17 years ago
|
Assignee: administration → nbezzala
Status: NEW → ASSIGNED
Target Milestone: Bugzilla 3.2 → Bugzilla 3.4
| Reporter | ||
Comment 10•17 years ago
|
||
Comment on attachment 379831 [details] [diff] [review]
added class "areyousure" and used it while deleting a custom field
>+p.areyousure {
The classed shouldn't be tied to <p>. It may be used with e.g. <div>.
>+ font-size: 120%;
>+ font-weight: bold;
Both should go away. We are not throwing an error, only a confirmation message.
Attachment #379831 -
Flags: review?(LpSolit) → review-
| Reporter | ||
Updated•17 years ago
|
Target Milestone: Bugzilla 3.4 → Bugzilla 3.6
Comment 11•16 years ago
|
||
Attachment #379831 -
Attachment is obsolete: true
Attachment #408587 -
Flags: review?(LpSolit)
| Reporter | ||
Comment 12•16 years ago
|
||
Delaying to 3.8, so that more places can use it. Having it in a single place only for 3.6 would be confusing.
Severity: normal → minor
Whiteboard: [Good Intro Bug]
Target Milestone: Bugzilla 3.6 → Bugzilla 3.8
| Reporter | ||
Comment 13•16 years ago
|
||
Comment on attachment 408587 [details] [diff] [review]
Fixed ".areyousure"
>Index: skins/standard/admin.css
>+.areyousure {
>+ background-color: red;
>+ color: black;
>+}
This class needs some padding and margin (both set to 1em seems good). Also, we should find a way to not have the whole line to have a red background, but only the part of it containing text (so if the text is short enough to fit in one third of the width of the window, then only one third of the width of the window should have a red background).
Attachment #408587 -
Flags: review?(LpSolit) → review-
| Reporter | ||
Updated•15 years ago
|
Target Milestone: Bugzilla 4.0 → Bugzilla 4.2
| Reporter | ||
Updated•15 years ago
|
Target Milestone: Bugzilla 4.2 → Bugzilla 5.0
| Reporter | ||
Comment 14•14 years ago
|
||
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.
I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
| Assignee | ||
Comment 15•13 years ago
|
||
Repatching it with, similar to "areyoureallyreallysure" css class used for confirmation messages but with some less emphasis on text.
Attachment #673537 -
Flags: review?(LpSolit)
| Reporter | ||
Updated•13 years ago
|
Attachment #364726 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #408587 -
Attachment is obsolete: true
| Reporter | ||
Comment 16•13 years ago
|
||
Comment on attachment 673537 [details] [diff] [review]
Patch-v1
>+.areyousure {
Let's name it .confirmation.
>+ color: red;
We want the background in red, not the text itself, see previous comments.
Attachment #673537 -
Flags: review?(LpSolit) → review-
| Reporter | ||
Updated•13 years ago
|
Assignee: nbezzala → administration
| Assignee | ||
Comment 17•13 years ago
|
||
This patch also takes care of Confirmation messages while deleting Product, version, component and milestone.
For Milestone case, it was already implemented in table, updated the code to use .confirmation class with <p> tag.
Attachment #673537 -
Attachment is obsolete: true
Attachment #682516 -
Flags: review?(LpSolit)
| Reporter | ||
Comment 18•13 years ago
|
||
Comment on attachment 682516 [details] [diff] [review]
Patch-v2
>=== modified file 'skins/standard/admin.css'
>+ padding: 3ex 3ex 3ex 3ex;
Nit: no need to repeat 3ex four times. Just once is enough.
r=LpSolit
Attachment #682516 -
Flags: review?(LpSolit) → review+
| Reporter | ||
Updated•13 years ago
|
Assignee: administration → joshi_sunil
Flags: approval4.4+
Flags: approval+
Summary: The confirmation thrown when deleting a custom field has no red background → The confirmation thrown when deleting a custom field, component, version or product must have a red background if the deletion affects bugs
Target Milestone: --- → Bugzilla 4.4
| Reporter | ||
Comment 19•13 years ago
|
||
Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/trunk/
modified skins/standard/admin.css
modified template/en/default/admin/components/confirm-delete.html.tmpl
modified template/en/default/admin/custom_fields/confirm-delete.html.tmpl
modified template/en/default/admin/milestones/confirm-delete.html.tmpl
modified template/en/default/admin/products/confirm-delete.html.tmpl
modified template/en/default/admin/versions/confirm-delete.html.tmpl
Committed revision 8502.
Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/4.4/
modified skins/standard/admin.css
modified template/en/default/admin/components/confirm-delete.html.tmpl
modified template/en/default/admin/custom_fields/confirm-delete.html.tmpl
modified template/en/default/admin/milestones/confirm-delete.html.tmpl
modified template/en/default/admin/products/confirm-delete.html.tmpl
modified template/en/default/admin/versions/confirm-delete.html.tmpl
Committed revision 8478.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•