Closed Bug 16479 Opened 25 years ago Closed 24 years ago

[Dogfood] Need titledbutton with fly-out menu

Categories

(Core :: XUL, defect, P1)

Product:
Core
Component:
XUL
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: german, Assigned: hyatt)

References

Details

(Whiteboard: [PDT+] 02/04-Checking on verification with UI) 

Need this new widget in for many buttons in mail and browser. The widgets
contains both of an action button area as well as of a fly-out menu trigger area
next to it.

Here is what we need (agreed on):
We need to be able to configure the menu to come out both at the left or right
side, and by default the menu should be aligned on a left aligned trigger area
and right-aligned on a right-aligned trigger area.
_______        _______
|V|____|       |____|V|
|Item1 |       |Item1 |
|Item 2|       |Item 2|
|Item 3|       |Item 3|
|______|       |______|

We also need to treat capture hover and mousedown events seperately for both
areas. The disabled state will affect the whole area. Backgrounds should be able
to span both areas.
Whiteboard: [PDT-]
Sorry, not a dogfood blocker.  Putting on [PDT-] radar.
Whiteboard: [PDT-] → PDT-
Jan, are you aware that without this we are either deciding that menus on
forward and back buttons (and others) are not needed for dogfood, or we are
committing to do throw-away work on timing loops to popup menus, that nobody
wants to do?
No not aware since this bug is marked as an enhancement and this is not clear in
the info.  Bug still marked as P3/Enhancement.  Please update these fields as
appropriate to the severity and importance of this bug.  I don't think we need
menus on our buttons in dogfood.  Others?
Severity: enhancement → critical
Priority: P3 → P1
updated marking to put back on the radar. We -really- do need this as soon we
can get it! Thanks.
to be more precise, mail will not be functional without, browser will need and
so does the editor/formatting toolbar. There are other place in dialogs where
this is needed too!
German, to get this back on the radar you need to either delete the PDT- or mail
to pdt@netscape.com.
Whiteboard: PDT-
-pdt deleted
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Good grief. I had this fixed before it was even filed. :)
:-)
Whiteboard: [PDT+]
putting on PDT+ in case it ever reopens.  Which it won't...but who knows...:-)

Claudius...can you verify this today please.
Whiteboard: [PDT+] → [PDT+] NOV-11 waiting on some clues to verify
as soon as someone finds such a widget anywhere in the app and points
it out to me i will be glad to test it. i know and can imagine where they are
supposed to be i just don't see any in my 1999111112 build.
I'll see that I can create a test XUL file next week. You're right we're still
working on the exact design, now that we have got hyatt's XUL implementation.
Whiteboard: [PDT+] NOV-11 waiting on some clues to verify → [PDT+] NOV-29 impossible to verify w/o testcase
patiently awaiting a testcase, just updating the whiteboard.
Whiteboard: [PDT+] NOV-29 impossible to verify w/o testcase → [PDT+] DEC-9 impossible to verify w/o testcase
been waiting a month now...
QA Contact: claudius → german
german can verifiy if he chooses
german, what's the latest on this?
Whiteboard: [PDT+] DEC-9 impossible to verify w/o testcase → [PDT+] 02/04-Checking on verification with UI
I would vote for removing the PDT+ attribute for now and reduce the severity. An 
earlier solution did not work out and wasn't even worth providing a test case as 
the technology was too limited to give us a properly designed/aligned menu 
button. With Hyatt's upcoming XBL mechanism on the horizon we'll have a good 
chance to be able to build these buttons, but after beta1! Once XBL gels we can 
provide a test case around m15/16?. Sorry for the delay but we had tried to build 
a good test case but it was just not ready for real-world consumption. If we see 
a problem then we can reopen the bug then OK?

Sounds good.  Marking Verified for now.
Status: RESOLVED → VERIFIED
*** Bug 28408 has been marked as a duplicate of this bug. ***
Using build 2000-04-11-08 on mac and -09 on win and linux mailnews has no menus 
for toolbar buttons so I'm going to reopen this for missing menus in the 3-pane 
window.  Specifically for the following buttons:
Forward (while a Mail msg is selected)
Reply (while a News msg is selected)
Reply All (whild a News msg is selected)
Next (when any mail message is selected)

I also noticed that the Browser doesn't have any fly out menus like in 4.7x, so 
I'm not sure if this is regression for Browser because I didn't test this.  If 
this bug is not for the sub menus for Toollbar buttons for all of the windows 
in the product, then state that and I will log a separate but for mail new menus 
that are missing.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Yes, please open new bugs for that, don't morph this into a front-end bug, it
was for the infrastructure work only.  resolving as fixed.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
Verifying per trudelle's comments and opening new bugs for mail&news toolbar 
butttons only.
Status: RESOLVED → VERIFIED
Blocks: 10096
You need to log in before you can comment on or make changes to this bug.