Closed Bug 48876 Opened 26 years ago Closed 26 years ago

D&D and modifier+click should be possible throughout the app

Categories

(SeaMonkey :: Sidebar, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.0

People

(Reporter: bugzilla, Assigned: bugzilla)

References

Details

(Whiteboard: [nsbeta3-])

Attachments

(4 files)

Build ID: 2000081308 There's no way to reload, bookmark, save, view the source of, or pretty much do *anything* with Sidebar tabs. This could be easily solved with the addition of a limited context menu (which wouldn't include navigational items like Back and Forward). I think the lack of Reload is the biggest killer here...how the heck do you manually reload the content?
How about allowing the sidebar content to have (visible) focus, and then having all items in the main toolbar and menu bar (except for Back and Forward) operating on the sidebar content?
works for me. Ideas on showing visible focus?
Showing a 1px black border around the inside of the sidebar content frame when it has focus. I think there's a bug asking to do the same thing to frames in the main content area, but it's been Futured. :-(
OS: Windows 98 → All
Hardware: PC → All
> works for me. Not for me. Clicking into a panel and hitting the reload button reload the main browser window, not the panel. blake's right - there's a lot of functionality in the browser that would be necessary or at least useful in the sidebar. E.g. support for the title attribute. Why can't we pretend, the sidebar panel were just another browser window/frame (technically, this means using the navigator overlays, I think)?
Keywords: nsbeta3
*** Bug 46276 has been marked as a duplicate of this bug. ***
nav triage team: cool ideas, some of this will be handled within the content (some folks adding "refresh" to the content of web side tabs), but bottom line these are new feature requests too late in the schedule so minus
Whiteboard: [nsbeta3-]
*** Bug 52008 has been marked as a duplicate of this bug. ***
reassigning to matt
Assignee: slamm → matt
Nominating for mozilla0.9. This bug is very annoying during sidebar development and usage. It would also fix a whole bunch of other existing bugs (I saw at least 5 or so).
Keywords: mozilla0.9
reassigning to me. I have a bunch of fixes for sidebar selection, d&d, context menus, modifier- and middle-click handling, and more.
Assignee: matt → blakeross
blake, can't we just reuse the browser functions?
Ben, which part of my comment suggested that I wasn't? But there are many changes that need to be made. The sidebar is in other apps besides the browser, and not all of those apps have access to browser functions.
Status: NEW → ASSIGNED
Priority: P3 → P1
Target Milestone: --- → mozilla1.0
> which part of my comment suggested that I wasn't? but > and not all of those apps have access to browser functions I'm confused.
I am reusing already-written browser functions, but generalizing them so they can be used in other places besides the browser.
Oh, cool. (I thought, they were already in this state.)
Attached a fix which also includes the partial patch for bug 50673 (cause it goes along with this). This fix implements d&d in the sidebar and in mail messages. It also allows for the standard modifier+click and middle-click handling in the personal toolbar, mail messages, sidebar, etc. I'll attach more patches soon for sidebar context menus. Meanwhile, I found out that you can in fact select text in the sidebar (because you can drag and then copy), but the selection itself isn't painted. I'm still trying to figure out why this is. Asking alecf to do some review here...
Keywords: approval, patch, review
blake, this rocks. I missed middle-click and d&d in mailnews msgs. For new files, shouldn't you name yourself, not Netscape, as "Inital Developer", even if you copied some functions from existing files?
Summary: Sidebar tab webpages have little (almost no) functionality → D&D and modifier+click should be possible throughout the app
This new patch fixes (partially) d&d to compose attachment tree and d&d into view source window also (there're separate bugs on those).
blakeross@telocity.com changed: What |Old Value |New Value ---------------------------------------------------------------------------- Summary|Sidebar tab webpages have |D&D and modifier+click |little (almost no) |should be possible |functionality |throughout the app (It's worth to log that here, since it is a drastic change in scope.) > d&d to compose attachment tree Cool. Does it also work for msgs? I.e. can I attach a msg (like it would if I |ForwardAsAttachment|) by dragging it from the thread pane to the attachment area, like I could in 4.x Unix?
> It's worth to log that here, since it is a drastic change in scope. Yeah. I haven't really decided what I'm going to do re: the original bug. Since I kinda changed it. Sorry, no, that message dragging doesn't work yet. But I haven't even looked into it yet. I suspect it's not all that hard.
> message dragging IIRC, it is the only way to forward more than one msg at once, so it would be really useful(TM).
alec, don't review just yet. I'll attach a new patch tomorrow with suggestions from jag.
This is great blake, but a few comments: - first, let's not make this "nodeclick.js" - lets make it "contentAreaUtils.js" or something - since this is basically for any kind of app that has a gecko content area. - second, I see at least one place where oncommand= became onclick= - oncommand= is the correct one - onclick just handles mouseclicks, oncommand handles keyboard activation as well.
> - first, let's not make this "nodeclick.js" - lets make > it "contentAreaUtils.js" or something - since this is basically for any kind > of app that has a gecko content area. hmm, okay. although it really is only for clicks, and nodeDD is for d&d... > - second, I see at least one place where oncommand= became onclick= - > oncommand= is the correct one - onclick just handles mouseclicks, oncommand > handles keyboard activation as well. The only place I changed this was for the personal toolbar items, so that we could get an event.button and handle middle click (oncommand is left click only, apparently). This should be fine, since toolbar buttons/items shouldn't take focus or be accessible via the keyboard...
Just to be clear: the click-handling and dnd-handling are in two separate files right now, nodeClick.js and nodeDD.js. I was thinking of putting them together (since right now I'm including both of them wherever they're used), but jag suggested breaking them apart.
thought about it a little more. I guess something like contentAreaUtils.js is pretty good, since the file does include other stuff (openNewWindowWith(), savePage(), etc)
Attached patch revised patch — — Splinter Review
Modified and middle click doesn't work on PT items in the new fix while alec, jag and I work out the best way to do it. [note to self: make clicks on home work also once we decide on a way]
r=jag Thanks for making my life merge hell soon ;-) (Poor shaver)
OK, part 1 checked in. I know this bug got heavily morphed, but I really reported it too generally to begin with. I'll file separate bugs for the selection and context menu problems, and start making fixes for those tomorrow.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Blake, I can't copy selections from some sidebar panels at all (bug 52010). What panel allows you to select&copy but doesn't show you the selection?
Blake, what are the bug numbers for those other bugs -- the lack of selection, the lack of context menus, and the inability to use {Back, Forward, Reload, view source, Use Style, etc} in a sidebar panel?
Lack of context menus is bug 18787 ...
Selection problem is bug 60988.
over to sujay
QA Contact: shrir → sujay
okay Reload is in the context menu....and I think it works.... Blake can y ou double check and see if its working...
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: