Opened 10 years ago

Last modified 3 weeks ago

#7062 assigned enhancement

Add "Open in new window" in context menu

Reported by: humdinger Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Applications/WebPositive Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


This is hrev547.

Context menus on links should offer to "Open in new window". ATM you can only open in new tab.

Change History (7)

comment:1 by leavengood, 10 years ago

Owner: changed from stippi to leavengood
Status: newassigned

Should be easy enough. I'll take this over.

comment:2 by pulkomandy, 7 years ago

Owner: changed from leavengood to pulkomandy

Not as easy as it looks. The menu is on WebKit side.

comment:3 by luroh, 6 years ago

Milestone: R1Unscheduled

Moving Web+ enhancements out of R1 milestone.

comment:4 by nephele, 13 months ago

On hrev53242 this functionality seams to be included, it seams to be broken since both options open links in a new in-window tab.

comment:5 by pulkomandy, 13 months ago

Yes, I started doing this, added the menu and then remembered that WebKit doesn't know the difference between "new tab" and "new window", that is entirely handled on the browser side.

Maybe webkit2 will allow us to move management of this menu outside of WebKit and have more control on what we put in it.

comment:6 by bitigchi, 3 weeks ago


I gotta ask, do other WebKit browsers use it this way? Safari always had the separation for this during its WebKit1 times. It sounds kind of weird to depend on the web rendering engine for application context menu.

Last edited 3 weeks ago by bitigchi (previous) (diff)

comment:7 by pulkomandy, 3 weeks ago

Well, we can change the context menu in WebKit so that's not exactly the problem. The problem is the WebKitLegacy API doesn't have (that I know) a distinction between tabs and windows. When you want to open a link you can specify "use this same tab/window", "use a new one", or "this is a download, don't open anything", and that's it.

I'm not sure Safari even used the WebKit1 API itself, this API was introduced for iOS apps to embed a web view or something like that and Safari probably did use more direct access to the WebKit internals. Which we could do as well, but at this point we should just shitch to WebKit2 and do this once we have migrated.

Note: See TracTickets for help on using tickets.