Closed Bug 306252 Opened 20 years ago Closed 15 years ago

XUL interface elements <menulist>/<menupopup> don't work

Categories

(Camino Graveyard :: HTML Form Controls, defect)

All
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: shy, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050828 Camino/0.9a2+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050828 Camino/0.9a2+ Actually, I don't know what would be the consequence of this bug on deploying a XUL app on the Mac, as it works correctly in Firefox/Mac — I haven't come to these detais yet. Still, a bug is a bug, right?! Reproducible: Always
Can you please provide more details about what the issue is? A testcase perhaps?
(In reply to comment #1) > Can you please provide more details about what the issue is? A testcase perhaps? I'm sorry, I thought it was self-evident. Just try the URL provided above. No dropdown list appears onclick. Nor is the list really navigable via keyboard either. But I've already noticed that the XUL implementation in Firefox is much more complete/acurate, so I'm not sure at all if implementing XUL for 3rd party use is a real objective in Camino.
Target Milestone: --- → Camino1.2
Mike gave it a target milestone, so confirming (I see the issues the reporter mentions on the URL above). My hosting provider has just redone their webmail in XUL, so it would be nice if I could actually get all of it working in Camino :-) That said, a statement on whether XUL webapps were supported in Camino or not would also suffice.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Josh, is this related to the popup stuff you were telling me about the other day on irc, or is this just another victim of "Camino's hacky select implementation"?
*** Bug 332250 has been marked as a duplicate of this bug. ***
This breaks ajaxsketch.com which is kinda hot right now.
Depends on: 306613
Josh, it'd be great if you could tell here for the record what the camino / xul-popup problem was/is, as I'm having trouble understanding the implications/reasons for this bug without that info. Thanks!
Target Milestone: Camino1.6 → Camino2.0
Mass-reassign of bugs still assigned to pinkerton to nobody; filter on "NoMoPinkBugsInCamino".
Assignee: mikepinkerton → nobody
QA Contact: form.controls
Target Milestone: Camino2.0 → ---
http://xulplanet.com/tutorials/xultu/examples/ex_lists_5.xul is (hopefully temporarily) dead at the moment, but I've added a link to the Mozilla XUL tutorial for menus that demonstrates this bug.
Remote XUL is dead in the era of HTML5, and I think we want to explicitly state we don't support it. The fact the Core continues to change the rules and pull the rug out from underneath us (e.g., we fixed bug 306613 using the event they told us to use, and then in 1.9.x they stopped firing events altogether, leaving us high and dry) makes content-area XUL more trouble than it's worth for everything that is not absolutely essential to the operation of the browser. I think this should be WONTFIX and be done with it.
In nearly five years of having this bug on file, we've seen exactly one real-world case where it breaks something, and even that's of dubious importance. I'm with Smokey.
Sounds good to me. WONTFIX.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.